Splunk Search

annotated raw field in transactions

Ledion_Bitincka
Splunk Employee
Splunk Employee

Dan Goldburt asks:

I'm consistently getting the following request from customers: "can I see where each event came from?". If they have this 150+ line transaction and want to scan through it, it helps to see the host, sourcetype, etc... next to each component event. (for a deep dive, I attached an email where I was working on this for another customer and couldn't come up with a satisfactory answer). Has anyone else heard this complaint?

Tags (1)

Ledion_Bitincka
Splunk Employee
Splunk Employee

A fairly crude way of seeing the source/sourcetype/host next to each individual event is to concat the value of those fields into _raw before doing the transaction, e.g.

… | eval _raw = source . “;” . sourcetype . “;” . host . “;” . _raw | transaction …

  • SteveZ
Get Updates on the Splunk Community!

[Puzzles] Solve, Learn, Repeat: Dynamic formatting from XML events

This challenge was first posted on Slack #puzzles channelFor a previous puzzle, I needed a set of fixed-length ...

Enter the Agentic Era with Splunk AI Assistant for SPL 1.4

  🚀 Your data just got a serious AI upgrade — are you ready? Say hello to the Agentic Era with the ...

Stronger Security with Federated Search for S3, GCP SQL & Australian Threat ...

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...