Splunk Search

How to Group Events at Index Time?

skoelpin
SplunkTrust
SplunkTrust

I want to tie together 2 events at index time the same way I would tie them together at search time using the transaction command.

So for example I have this..

Mon Jul 11 13:57:29 2016
RW(16,148936) report:
RW: DBdelete return -1; fname=CM,key=01*123/456-7890


Mon Jul 11 13:57:29 2016
RW(16,148936) report:
Delete CM,'01*123/456-7890' failed

I created a field called key which will grab 01*123/456-7890 from both events and I can tie them together at search time using transaction.. index=sql | transaction Key.. But I want to do this at index time instead so the end user does not have to keep tieing them together with the transaction command each time they do a search

Tags (2)
0 Karma
1 Solution

skoelpin
SplunkTrust
SplunkTrust

What a bummer. I guess I could go that route or just use the transaction command as a saved search so they don't have to type it in each time

View solution in original post

0 Karma

skoelpin
SplunkTrust
SplunkTrust

What a bummer. I guess I could go that route or just use the transaction command as a saved search so they don't have to type it in each time

0 Karma

somesoni2
Revered Legend

Or as a macro. You can also look at option of summary indexing just in case users don't need this data in real-time.

skoelpin
SplunkTrust
SplunkTrust

This is what I'll do! I'm willing to wait a half hour if it means I can get a performance boost at search time, thanks!

0 Karma
Get Updates on the Splunk Community!

Celebrating Fast Lane: 2025 Authorized Learning Partner of the Year

At .conf25, Splunk proudly recognized Fast Lane as the 2025 Authorized Learning Partner of the Year. This ...

Tech Talk Recap | Mastering Threat Hunting

Mastering Threat HuntingDive into the world of threat hunting, exploring the key differences between ...

Observability for AI Applications: Troubleshooting Latency

If you’re working with proprietary company data, you’re probably going to have a locally hosted LLM or many ...