Getting Data In

Summary index syslog events doing line merge

vcarbona
Path Finder

A colleague of mine is summary indexing syslog events from a bigger syslog index. He's doing this to have a more focused and quicker search of the data. However, the syslog events in the summary index are merging from time to time which makes reporting by field impossible. I know with regular indexes there is a SHOULD_LINEMERGE configuration setting, but is there a way to configure the summary index that way? I'm afraid to break something if I add a "SHOULD_LINEMERGE = False" to the "stash" sourcetype.

Additional question: Is it appropriate to put entire events into a summary index? I always thought that summary indexing was used to store aggregated data and not actual entire events.

0 Karma

hazekamp
Builder

vcarbona,

You are correct in that summary indexes typically contain aggregated data and not actual events.

If you desire a smaller subset of actual events consider creating an index to route specific events based on some criteria.

I would not recommend changing any of the default behavior for the stash sourcetype as this is likely to have adverse affects.

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!

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 ...

Splunk Auto Ingestion Parallel Pipeline Scaling

Why this feature matters Many Splunk environments experience ingestion pressure long before the host is fully ...