After upgrading my Windows servers 2003 to Splunk 6. I discovered that all my nullQueues filter stopped working, and I indexed mode data than before.
I checked, and the reason is that the sourcetype name for the WinEventLog has a different case for the first letter of the channel :
became under Splunk 6 for Win 2003 only
FYI my filter on the indexers and heavy forwarders were :
REGEX = (Windows Update)
DEST_KEY = queue
FORMAT = nullQueue
This is a known bug SPL-78726, the fix is not yet released in Splunk 6.0 or 6.0.1
For the search, the sourcetypes are case insensitive, so you will find the events.
But for the props.conf matching the regex and stanza are case sensitive, so they may not apply anymore.
As you wish,
- system/local will always win, so this is a very definitive place to change
- While an app can be deployed easily to all instances using a deployment server
So do we change the props.conf on the forwarder or indexer? Also, are these two separate workarounds that will solve the issue or are they to be used together?
the indextime filters only applies on the instances parsing the events : Indexers and Heavy forwarders (if any)
If you had custom props.conf that were working, change they were they already exist.
Thank you for your response however I'm not sure what you're saying here could you please clarify?