In addition, look under the "Storage requirement examples" section at the following link for splunk indexer clusters.: http://docs.splunk.com/Documentation/Splunk/6.2.4/Indexer/Systemrequirements
... View more
ahh, just add those cases in the case statement like so
sourcetype="socialist action" "government" OR "govern" OR "race" OR "racist" | eval word = case(word=="racist","race", word =="govern", "government", word =="government", "government", word=="race", "race") | stats count by word
... View more
Try this:
sourcetype="socialist action" "government" OR "govern" OR "race" OR "racist" | eval word = case(word=="racist","race", word =="govern", "government") | stats count by word
EDIT: assuming you have a field named "word" already extracted/populated
... View more
This might work:
earliest=-2w latest=-d index=int sourcetype=threat NOT [search earliest=-4w latest=-2w index=int sourcetype=threat | stats count by name | sort -count | head 10 | table name ] | stats count by name | sort -count | head 10 | table name
... View more
Have you tried reading up on Field Extractions in Splunk?
Ref: http://docs.splunk.com/Documentation/Splunk/6.2.3/Knowledge/ExtractfieldsinteractivelywithIFX
You can also specify transforms for your data ( transforms.conf + props.conf)
Ref: http://docs.splunk.com/Documentation/Splunk/6.2.3/Knowledge/Createandmaintainsearch-timefieldextractionsthroughconfigurationfiles
... View more
FWIW, I use splunk 6.2.2 and had a csv file with a field named source. It got converted to extracted_source. you could simply rename the field in your logs or rename extracted_source to something else using the rename command.
... View more
In addition to this (quite comprehensive) answer, please be aware of what gets replicated across search head cluster and what doesn't. In general knowledge-objects get replicated, for everything else use the deployer to maintain consistency across search heads. If you are not careful with this, you'll end up with search heads with inconsistent settings.
For reference: http://docs.splunk.com/Documentation/Splunk/6.2.3/DistSearch/HowconfigurationworksinSHC
... View more
Ahh....ui_inactivity_timout specifies interval when notification is sent. You also need to update tools.sessions.timeout in the same conf file. I misread the documentation.
... View more
Check the answer posted here:
http://answers.splunk.com/answers/38832/how-do-i-set-up-the-s-o-s-app-to-monitor-splunks-system-resource-consumption.html
Also, check the following answer for best practices.
http://answers.splunk.com/answers/38091/best-practices-to-deploy-the-s-o-s-app-in-a-distributed-search-environment.html
... View more
Check out web.conf, particularly the setting under ui_inactivity_timeout.
Ref: http://docs.splunk.com/Documentation/Splunk/6.2.3/admin/Webconf
... View more
As per the documentation, Splunk will check against all configured access strategies. By default, it searches Splunk local users first and then any other strategy configured.
(Ref: http://docs.splunk.com/Documentation/Splunk/latest/Security/ConfigureSplunkToUsePAMOrRADIUSAuthentication )
... View more
True. It also could be related to the timing. When monitoring for each file/index started. Having said that, you don't really need a confirmation if you test it with different sources. Your real world use-case won't ever have same data! My 2 cents.
... View more
Splunk performs a CRC check on a small portion of the file to check if it has already been indexed. May be this is why it is not being re-indexed. Try changing the file contents or use different files.
... View more
Search head distributes the search to all peers and combines the results. So you'll see results from both. (if it matches the search query ofcourse!)
... View more
I think you should look at the other option. You could make it a non clustered search peer and then retire it once the data on it becomes too old. New data will anyway be getting indexed on the new system.
... View more