Splunk Search

Sumo Transaction States to Splunk Query

parkertctr
Path Finder

Good Day, I am trying to come up with ideas to translate a Sumo Trasactional search with (States) Conditions to a Splunk Query.  If anyone can provide some other options, please let me know.  

Here is my sample Sumo search:

_sourceCategory=prod/app/m/* and "statement" and ("Search Keys" or "STATUS=ERROR" or Error)
| parse "[ID=*]" as MID nodrop
| transactionize MID (merge MID takeFirst, _raw join with "\n\n")
| transaction on ORGID, EVENT, ORDER, FACILITY with "*A request to obtain a channel subscription failed*" as NO_SUB, with "*M cannot be discontinued*" as NO_DC, with "*Person not found*" as NO_PERSON

| (NO_SUB + NO_DC + NO_PERSON) as Total
| fields ORGID, EVENT, ORDER, FACILITY, Total, NO_SUB, NO_DC,NO_PERSON
| sort by Total, ORGID, EVENT, ORDER
//| sort by ORGID, EVENT

Splunk Search so far:

index=hhh_m_prod sourcetype=mirth* MID=* CID=* acctnumber=* facility=* orgid=* "Statement" ("Search Keys" OR "STATUS=ERROR" OR "Error")
| fillnull value="NULL" | transaction MID
| eval NO_DC=if(match(_raw, "M cannot be discontinued*"), "Yes", "No")
| eval NO_SUB=if(match(_raw, "A request to obtain a channel subscription failed*"), "Yes", "No")
| eval NO_PERSON=if(match(_raw, "Person not found*"), "Yes", "No")

| transaction ORGID EVENT ORDER FACILITY
| eval Total=sum(NO_SUB, NO_DC, NO_PERSON
| table ORGID, EVENT, ORDER, FACILITY, Total, NO_SUB, NO_DC,NO_PERSON 
| sort by Total ORGID EVENT ORDER | sort by ORGID, EVENT

** I am lost for ideas in running the conditional transaction statements... Should I use more eval statements, or setup a transactiontypes.conf?  

Labels (2)
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 ...