Getting Data In

Notable Event Metrics / SLA Tracking? (Dwell Time, Time To Respond, etc)

AndySplunks
Communicator

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.

0 Karma
1 Solution

AndySplunks
Communicator

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)"

View solution in original post

0 Karma

AndySplunks
Communicator

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)"
0 Karma

rroberts
Splunk Employee
Splunk Employee

What version of ES are you on?

0 Karma

AndySplunks
Communicator

I'm on version 3.3.1.

0 Karma
Get Updates on the Splunk Community!

Improve Your Security Posture

Watch NowImprove Your Security PostureCustomers are at the center of everything we do at Splunk and security ...

Maximize the Value from Microsoft Defender with Splunk

 Watch NowJoin Splunk and Sens Consulting for this Security Edition Tech TalkWho should attend:  Security ...

This Week's Community Digest - Splunk Community Happenings [6.27.22]

Get the latest news and updates from the Splunk Community here! News From Splunk Answers ✍️ Splunk Answers is ...