Getting Data In

Starting point of index

n_greder
New Member

Hello,

i would like to add a monitor for EventLog:Security.
This EventLog contains many entries, and if i add it directly, i know that Splunk will index thousand of event, and my 500Mb will be consumed for.

So i see in tutorial that is was possible to choose at what time Splunk begin to index event with the following line in inputs.conf:

[WMI:WinEventLog:Security]
disabled = 0
start_from = newest
current_only = 1

I have a question:
The only means to succeed is to use only the inputs.conf file? Because if i use Splunk Web, it starting to index all events from eventlogs, so i have to prepare my inputs.conf file before, no?

Thx for your help

0 Karma
1 Solution

MHibbin
Influencer

That's kind of correct... modifying inputs.conf is the way to go (make sure you restart Splunk to apply the changes), however your config is slightly wrong, you should try:

[WMI:WinEventLog:Security]
disabled = 0
start_from = oldest
current_only = 1

This will just read from the oldest to newest (i.e. normal cronological flow), but only starting from the first event, from when the input is enabled (i.e. restart Splunk to apply config). At the moment you have it backwards, as it will read in reverse chronological order and then go back to the latest, which doesn't make sense.

HOWEVER... although you may exceed your daily limit, Splunk will not punish you for you first offence, as in a real world there are times when we find the unexpected, and perhaps your logging source goes rogue and pumps out gigs of data. You should read the following doc, as indexing some of you older/historic events may be useful in showing Splunk's potential...

http://docs.splunk.com/Documentation/Splunk/5.0/Admin/Aboutlicenseviolations

Hope this helps

View solution in original post

MHibbin
Influencer

That's kind of correct... modifying inputs.conf is the way to go (make sure you restart Splunk to apply the changes), however your config is slightly wrong, you should try:

[WMI:WinEventLog:Security]
disabled = 0
start_from = oldest
current_only = 1

This will just read from the oldest to newest (i.e. normal cronological flow), but only starting from the first event, from when the input is enabled (i.e. restart Splunk to apply config). At the moment you have it backwards, as it will read in reverse chronological order and then go back to the latest, which doesn't make sense.

HOWEVER... although you may exceed your daily limit, Splunk will not punish you for you first offence, as in a real world there are times when we find the unexpected, and perhaps your logging source goes rogue and pumps out gigs of data. You should read the following doc, as indexing some of you older/historic events may be useful in showing Splunk's potential...

http://docs.splunk.com/Documentation/Splunk/5.0/Admin/Aboutlicenseviolations

Hope this helps

n_greder
New Member

Hello MHibbin,

ok, about newest and oldest i had a doubt to understand clearfully the explanation in admin guide, but as my boss said that were possible to index only since a specific date...

Thx for your answer and have a nice day

0 Karma

bmacias84
Champion

As Note: current_only = 1 will only capture events while the Splunk service is running. Alternatively you could write you own specific WMI query for the event log that pull events after a certaint date.

WMI QUERY:


Select * from Win32_NTLogEvent Where Logfile = 'System' AND TimeWritten >= '20121101000000.000000-36'

'20121101000000.000000-36' is year=2012,month=11,day=01

Get Updates on the Splunk Community!

Introducing the 2024 SplunkTrust!

Hello, Splunk Community! We are beyond thrilled to announce our newest group of SplunkTrust members!  The ...

Introducing the 2024 Splunk MVPs!

We are excited to announce the 2024 cohort of the Splunk MVP program. Splunk MVPs are passionate members of ...

Splunk Custom Visualizations App End of Life

The Splunk Custom Visualizations apps End of Life for SimpleXML will reach end of support on Dec 21, 2024, ...