Splunk Search

SubSearch - Selecting the last mention of an incident number

ervinsmith
Explorer

Example: a series of events all have the same incident number (1170820) outlining the lifecycle of the ticket (from open to close).

I want to be able to create a field for when the incident was closed so that the time can be easily identified on a dashboard.  (Time | Closed Time | Computer Name | ETC).

How can I isolate a sub-search to track the latest ticket in a series of incidents so that I can set a field for "Closed time"?

 

subsearch.PNG

Labels (4)
0 Karma
1 Solution

sharynh
Splunk Employee
Splunk Employee

Is there anything in the event that indicates that the ticket has been closed? also, have you looked at the Transaction command

Customer Success Manager | Public Sector
Splunker since July 2021 - still a newbie!

View solution in original post

Tags (1)
0 Karma

sharynh
Splunk Employee
Splunk Employee

Is there anything in the event that indicates that the ticket has been closed? also, have you looked at the Transaction command

Customer Success Manager | Public Sector
Splunker since July 2021 - still a newbie!
Tags (1)
0 Karma

ervinsmith
Explorer

Also, for the Open-Close state, I used an eval + convert to reformat the seconds format it spits out:

| eval Incident_Opened=_time, Incident_Closed=_time + duration
| convert timeformat="%m-%d-%Y %l:%M:%S %p" ctime(Incident_Opened), ctime(Incident_Closed)

0 Karma

ervinsmith
Explorer

Took a bit of research and testing but transactions turned out to be what I needed.

Ended up settling on:

| transaction incident_number, query with mvlist=t

Tags (1)
0 Karma
Get Updates on the Splunk Community!

Index This | What’s a riddle wrapped in an enigma?

September 2025 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with this ...

BORE at .conf25

Boss Of Regular Expression (BORE) was an interactive session run again this year at .conf25 by the brilliant ...

OpenTelemetry for Legacy Apps? Yes, You Can!

This article is a follow-up to my previous article posted on the OpenTelemetry Blog, "Your Critical Legacy App ...