We have a need to exclude unwanted events from indexing. The problem is the majority of them are windows file access events which we need to monitor.
What i need to know is if we can exclude eventlogs from indexing based on a process ID or the application running them.
The backup is causing lots of unnecessary events that need excluding.
What do the events look like? What is the sourcetype and the format? What uniquely identifies these events?
Also, have you considered setting the Windows application log to exclude these events? If Windows isn't logging the details, then Splunk won't either.
Many thanks for your reply Iguinn,
However my problem is this.
I need to index read and write events (which we are currently) but I want to exclude read and write events logged by a particular process (the backup application)
at the moment the backup application is accounting for 95% of all indexed items and there is no requirement for us to keep those indexed.
Can you help further ?
The answer to your question is yes. In Splunk, this is called filtering. Filtering is performed as the input data is parsed. Usually this happens on the indexer (unless you are using a heavy forwarder).
Here is a link to the relevant bit of documentation: Route and filter data
Here are some similar questions at answers.splunk.com, which show examples that may be useful to you
Hopefully this will help. Feel free to ask more specific questions if you need more details.