topic Re: Why is nullQueue configuration not working? in Getting Data In

Why is nullQueue configuration not working?

wegscd — Fri, 22 Aug 2014 21:28:55 GMT

/opt/splunk/etc/system/local/transforms.conf

[WhirlpoolMWGBad]
REGEX=200
DEST_KEY=queue
FORMAT=nullQueue

/opt/splunk/etc/system/local/props.conf

[WhirlpoolMWGLog]
NO_BINARY_CHECK = 1
SHOULD_LINEMERGE = false
pulldown_type = 1
TRANSFORMS-WhirlpoolMGWBad = WhirlpoolMGWBad

splunkd is restarted.

lines containing '200' should not get indexed, but they are still getting indexed. What am I missing?

Re: Why is nullQueue configuration not working?

strive — Sat, 23 Aug 2014 02:23:31 GMT

Can you post your sample log event?

Re: Why is nullQueue configuration not working?

MuS — Sat, 23 Aug 2014 06:47:41 GMT

Does your sourcetype match exactly?

Re: Why is nullQueue configuration not working?

starcher — Sat, 23 Aug 2014 19:32:08 GMT

Have you made sure the props and transforms are on all of your indexers? For Nullqueue work it needs to be on the indexers receiving the events.

Re: Why is nullQueue configuration not working?

Ayn — Sun, 24 Aug 2014 15:57:49 GMT

You have a transform name mismatch between your props.conf and transforms.conf. In props.conf you call the transform "WhirlpoolMGWBad" whereas you call the transform "WhirlpoolMWGBad" (you've switched the W and G) in transforms.conf.

Re: Why is nullQueue configuration not working?

wegscd — Mon, 25 Aug 2014 13:36:30 GMT

d'oh! must have looked at that 5 times. Thank you for that.

is there a way to change the logging levels so that Splunk will log if a non-existent stanza is referenced?