SLA and ROI Widgets

Last Updated: November 16, 2026

Overview

D3 Morpheus includes ready-made reporting widgets for two questions every SOC is asked: how fast threats are detected and resolved (SLA widgets), and how much time and money automation saves (ROI widgets). Add them to any reporting dashboard, or start from the system sample Dashboard Sample - SLA.

Reporting dashboards are under Configuration > Reporting Dashboard > Dashboards.

The sample SLA dashboard

Dashboard Sample - SLA showing Mean Time to Resolve By Owner, Average Detect Time, Mean Time to Detect By Incident Type, Average Resolve Time and Top 50 Long Running Incidents

SLA Widgets

Widget

Type

What it shows

Default period

Average Detect Time

Number

The average time from an event happening to its detection.

Last 30 days

Average Resolve Time

Number

The average time from an incident being created to it being closed.

Last 30 days

Detect Time By Day

Line chart

Detection time, day by day.

Last 14 days

Event Detect Time By Severity

Bar chart

Detection time for each severity: Critical, High, Medium and Low.

Last 14 days

Mean Time to Detect By Incident Type

Bar chart

The average detection time for each incident type.

Last 30 days

Mean Time to Resolve By Incident Type

Column chart

The average resolution time for each incident type.

Last 30 days

Mean Time to Resolve By Owner

Bar chart

The average resolution time for each incident owner.

Last 14 days

Top 10 Average Detect Time By Incident Type

Column chart

The ten incident types that take longest to detect.

Last 30 days

The sample dashboard also shows Top 50 Long Running Incidents, the incidents open longest, and the widget panel lists Resolved Incidents Count By Day beside the SLA widgets.

Detection time is only as accurate as the event's own time. See Field Names below.

ROI Widgets

Widget

What it shows

Total Saved Hours

The analyst time automation has saved: every utility and integration command run, multiplied by the time each run saves, as set in the ROI configuration.

Total Saved Money (USD)

The same savings in dollars, using Cost saved per command run (dollars) from the ROI configuration.

Both widgets show a running total of every command run up to now.

The time and cost saved per command run are set under Global Settings > Application Settings > Return on Investment (ROI) Configuration. The page lists Integration Commands and Utility Commands; Only show configured narrows the list to the commands that have values.

  • Set ROI Defaults sets the defaults for all commands: Time saved per command run (minutes) and Cost saved per command run (dollars), once under Integration Commands ROI Default and once under Utility Commands ROI Default.

  • Select an individual command to override these defaults for that command.

Adding the ROI Widgets

  1. Go to Configuration > Reporting Dashboard > Dashboards and select New Dashboard.

  2. Name the dashboard, and choose a site and dates at the top.

  3. In the widget panel on the right, search for Saved. Both widgets are listed under NUMBER WIDGETS.

  4. Drag Total Saved Hours and Total Saved Money (USD) onto the canvas.

  5. Select Save.

Searching the widget panel

The widget panel searched for Saved, listing Total Saved Hours and Total Saved Money (USD) under Number Widgets

The ROI widgets on a dashboard

A new dashboard with the Total Saved Hours and Total Saved Money (USD) widgets on its canvas

The SLA widgets are added the same way: search for Detect or Resolve.

Widget Example: FTE Gained

FTE Gained estimates how much analyst capacity automation recovers, expressed as full-time equivalents (FTE). An HTML widget counts the events that were dismissed automatically, multiplies them by the minutes an analyst would have spent on each one, and divides the hours saved by one analyst's working hours for the same period. The widget's template does the calculation, so the figure is the same every time the dashboard loads.

FTE Gained is an estimate based on event counts and the time values you agree on. It is calculated differently from Total Saved Hours, which adds up the ROI time set on each command, so the two figures will not match.

How FTE Gained Is Calculated

  • Hours saved = events dismissed automatically × minutes saved per event ÷ 60

  • FTE Gained = hours saved ÷ (analyst hours per month × days in the date range ÷ 30)

For example, over 7 days with 2,100 events dismissed automatically and 5 minutes saved per event, hours saved = 2,100 × 5 ÷ 60 = 175. With 150 productive analyst hours per month, one analyst works 150 × 7 ÷ 30 = 35 hours in 7 days, so FTE Gained = 175 ÷ 35 = 5.0.

Before You Begin

Agree on two values with your SOC lead:

  • Minutes saved per event: how long an analyst takes to triage one event by hand, for example 5.

  • Analyst hours per month: productive hours one analyst works in a month, for example 150.

Then decide on the date range the widget will cover, for example the last 7 days. The template needs the number of days in that range.

Step 1: Create the Query

  1. Go to Configuration > Reporting Dashboard > Queries and select New Query.

  2. Set Data source to Event.

  3. Select the site.

  4. Set the date range to Last 7 days.

  5. Select Field, choose Dismissed Automatically, leave the operator as =, and set the value to true.

  6. Select Run Query. Each row is one event that was dismissed automatically.

  7. Enter a query name, for example Events Dismissed Automatically, and select Save.

Step 2: Create the HTML Widget and Its Measure

This step uses a measure, which is one figure worked out from a widget's queries. For how measures work, see Widget Measures and Template Logic.

  1. Go to Configuration > Reporting Dashboard > Widgets and select New Widget.

  2. Under Widget type, select Select a chart type and choose HTML.

  3. Under Queries, select Select a query and choose the query from Step 1. It becomes query A.

  4. Under Measures, rename the measure from Value to Auto-dismissed events. Keep A and COUNT. Its template name is auto_dismissed_events.

Name the measure before you write the template. The template refers to the measure by its template name, which is fixed when the widget is first saved.

Step 3: Write the Template and Save

In HTML Template, replace the example text with the template below. Replace 5 and 150 with the values you agreed on, and 7 with the number of days in the widget's date range. For what a template can use, such as round, comparisons and the {% else %} branch, see Widget Measures and Template Logic.

{% set hours = auto_dismissed_events * 5 / 60 %}
{% set fte = hours / (150 * 7 / 30) %}
{% if fte >= 0 %}
<p style="font-size: 28px"><b>{{ fte | round(1) }} FTE gained</b></p>
<p>{{ auto_dismissed_events }} events dismissed automatically in the last 7 days, about {{ hours | round(0) }} analyst hours saved.</p>
{% else %}
<p style="color: gray">No data for this period</p>
{% endif %}

The preview beside the editor shows the result. The last branch shows No data for this period when the count cannot be worked out.

A template cannot read the length of the date range, so the 7 in the template is fixed. If you change the query's range, turn on Override on the widget, or show the widget on a dashboard with its own date range, change the 7 in both places in the template to the new number of days. Otherwise the figure is wrong: the same count over 30 days divided by 7 gives an FTE Gained about four times too high.

To finish:

  1. Select the pencil beside New Widget, enter a widget name, for example FTE Gained, then select Save.

  2. Add the widget to a dashboard.

Step 4: Check the Figure

Work out one figure by hand: take the row count from Run Query in Step 1 and apply the formula above, then compare it with the widget. They should match.

The widget counts records instead of reading them, so it has no row limit. With Multi-Tenant, it adds up the counts from each tenant site before the template works out the figure.

Field Names

SLA widgets measure time between these fields. Each has a different name depending on where it is shown.

Field

Meaning

Where it appears

EventUTCTime

When the source system (for example Gmail or Splunk) created the event.

Event Utc Time in a query's dataset; Start Time (UTC) in an event's details.

IngestedUTCTime

When D3 Morpheus created the event record.

IngestedUTCTime in a query's dataset; Intake Time (UTC) in an event's details.

CreatedUTCTime

When the incident was created.

Date Created (UTC) in the incident list and the incident's overview.

ClosedUTCTime

When the incident was closed.

Date Closed in the incident list and the incident's overview.

If the source does not provide the event's own time, Start Time (UTC) is empty and detection time falls back to IngestedUTCTime. To fill it, map the original event's time field to the system field Start Time in the event field mapping.

The Events list does not show Time of Occurrence (UTC) by default. To add it, select the more icon (⋮) at the top right of the list, then Columns, tick Time of Occurrence (UTC) and select Apply.