Join the Conversation
- Find Answers
- :
- Splunk Administration
- :
- Getting Data In
- :
- Re: Notable Event Metrics / SLA Tracking? (Dwell T...
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark Topic
- Subscribe to Topic
- Mute Topic
- Printer Friendly Page
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Has anyone ever written any dashboards for analyst metrics around responding to notable events?
I'm primarily looking at trying to write a search to determine time to respond to a new notable event as well as time to close as well as tracking notable events still open per day.
The Incident Review audit is good for looking at what sorts of events are being opened, but is lacking on the response.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I wrote this for average response time as well as the standard deviation for a chart of how fast events are being closed. Clearly you could modify the status_group portion to use a different field for detecting when an event is responded to.
`notable` | search NOT `suppression` status_group=Closed info_search_time=* review_time=* | eval response=(review_time-info_search_time)/60/60/24 | bin _time span=2w | stats avg(response) as "Avg (Days)", stdev(response) as "Std Dev (Days)" by urgency, _time | eval "Avg (Days)"=round('Avg (Days)',1) | eval "Std Dev (Days)"=round('Std Dev (Days)',1) | rename urgency as "Notable Event Urgency" | search "Notable Event Urgency"=critical OR "Notable Event Urgency"=high OR "Notable Event Urgency"=medium | table "Notable Event Urgency" _time "Avg (Days)" "Std Dev (Days)"
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I wrote this for average response time as well as the standard deviation for a chart of how fast events are being closed. Clearly you could modify the status_group portion to use a different field for detecting when an event is responded to.
`notable` | search NOT `suppression` status_group=Closed info_search_time=* review_time=* | eval response=(review_time-info_search_time)/60/60/24 | bin _time span=2w | stats avg(response) as "Avg (Days)", stdev(response) as "Std Dev (Days)" by urgency, _time | eval "Avg (Days)"=round('Avg (Days)',1) | eval "Std Dev (Days)"=round('Std Dev (Days)',1) | rename urgency as "Notable Event Urgency" | search "Notable Event Urgency"=critical OR "Notable Event Urgency"=high OR "Notable Event Urgency"=medium | table "Notable Event Urgency" _time "Avg (Days)" "Std Dev (Days)"
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
What version of ES are you on?
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm on version 3.3.1.
Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!
Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.
Your Path to AgenticOps: AI Experiences for Every Splunk Practitioner
The Data Connection - October 2026
Beyond the Acceleration Zone: Maximizing Your Success with Splunk Customer Experience ...
