I'm trying to follow the instructions from the "Route and filter data" section of the documentation. The server in question is Windows 2003 and it is using WMI to pull events from two Windows 2008 servers. The goal is to only capture account lockout events (event id: 644 on 2003 and event id: 4047 on 2008).
I followed the instructions, but it's causing all events to get dropped. If I remove the props.conf and transforms.conf, it pulls events just fine. Here are the config files:
[WinEventLog:Application] disabled = 1 [WinEventLog:Security] disabled = 0 [WinEventLog:System] disabled = 1 [script://$SPLUNK_HOME\bin\scripts\splunk-wmi.path] disabled = 0
[setnull] REGEX = . DEST_KEY = queue FORMAT = nullQueue [2008lockouts] REGEX = (?m)^EventCode=(4740)\b DEST_KEY = queue FORMAT = indexQueue [2003lockouts] REGEX = (?m)^EventCode=(644)\b DEST_KEY = queue FORMAT = indexQueue
[wmi] TRANSFORMS-null = 2008lockouts,setnull (note, I also tried it with TRANSFORMS-wmi) [WinEventLog:Security] TRANSFORMS-null = 2003lockouts,setnull
[settings] max_backoff = 300 heartbeat_interval = 500 max_retries_at_max_backoff = 50 result_queue_size = 1000 initial_backoff = 30 checkpoint_sync_interval = 2 [WMI:2008DCEventLogs] disabled = 0 event_log_file = security interval = 10 server = server1, server2
What am I doing wrong here?
What happens if you reverse the order in the transform line?
[wmi] TRANSFORMS-null = setnull, 2008lockouts [WinEventLog:Security] TRANSFORMS-null = setnull, 2003lockouts
The order in transforms.conf shouldn't matter, but the order in the actual
TRANSFORM= line of props.conf may be significant. I think in your original version,
setnull will match after
200Xlockouts, so it will first set the queue to
indexQueue, but then change it back to
nullQueue when your single-dot regex matches.
Yes, the order does matter. Each individual transformer listed will be executed in the order given. (If you have multiple
transforms-<class> entries, then they will be in evaluated in ASCII sort order, FYI)