Splunk Search

Combining events into one

echalex
Builder

We're experiencing a problem with having indexed data with the default MAX_EVENTS value of 256. While this can be fixed in the configuration for new events, is there any way of combining e.g. a java stack trace of say 2000+ lines, which has been split up into tens of events, when searching?

Since we have already indexed a whole lot of logs, I'd hate to re-index it all again.

Tags (2)
1 Solution

hazekamp
Builder

echalex,

Unfortunately, If you have indexed data based on non-optimal or incorrect line breaking, there is not much that can be done via search to reliably reconstruct your data. You may be able to use the "transaction" command to create a single event as long as each event matches the criteria you are using to build the transaction.

For instance if you wanted to create a single event from multiple events from the same source, same time, and had some type of additional identifier like java_id:

| transaction _time,source,java_id 

View solution in original post

hazekamp
Builder

echalex,

Unfortunately, If you have indexed data based on non-optimal or incorrect line breaking, there is not much that can be done via search to reliably reconstruct your data. You may be able to use the "transaction" command to create a single event as long as each event matches the criteria you are using to build the transaction.

For instance if you wanted to create a single event from multiple events from the same source, same time, and had some type of additional identifier like java_id:

| transaction _time,source,java_id 

echalex
Builder

I noticed I hadn't thanked you for the informative answer.
So thank you. 🙂 (Better late than never, eh?)

0 Karma

merugu448
Engager

Thank you!!

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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...