Knowledge Management

Problem with NULL eventtype w/ summary index

emechler
New Member

I have a summary index that is being populated correctly via a scheduled query (or so it would seem). Here's the scheduled query:

index=web sourcetype=weblog | sitimechart span=1day count BY eventtype usenull=f

If I lookup all of the entries in the summary index, I see events that contain the 2 available eventtypes (http_allow and http_deny). However, running a timechart query against the summary index only produces data with NULL eventtype:

index=summary | timechart span=1day count by orig_eventtype

(if I include the usenull=f option then I get no data returned). Running the analogous timechart query against the web index will produce the correct result:

index=web_proxy | timechart span=1day count by eventtype usenull=f

Any ideas why my summary index appears to be ignoring the eventtype?

Thank you!

Tags (2)
0 Karma

emechler
New Member

Went to the gym to clear my head... the problem was that even though the eventtype was being put into the summary index event, the eventtype knowledge object wasn't being attached to the event since the necessary kv objects weren't being brought over as well. I just setup a new eventtype specific to the summary index and that fixed the problem.

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Vibe-coding, AI, and Splunkcraft: Highlights from the .conf26 Builder Bar

If you stopped by the Builder Bar at .conf26, thank you! This year, we brought ...

Thanks for the Memories: .conf26 Took Learning to New Heights

Thank you, Splunk Community, for making .conf26 in Denver one for the books. From packed Splunk University ...

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...