Skip to main content

Measure Engineering Efficiency

Scenario​

Your engineering manager asks: "How much investigation work is OpsWorker taking off the team, and how do we see it?"

How OpsWorker Helps​

Dashboard​

The Dashboard in the OpsWorker portal reports a focused, honest set of metrics, filtered by cluster and date range:

  • Alerts by status: how many alerts were received and where they ended up (for example, investigated versus not).
  • Finished investigations: how many investigations completed, per cluster, over the selected period.
  • Time saved in minutes: an estimate of the manual investigation time OpsWorker absorbed.

These are the metrics that actually ship. The Dashboard does not compute MTTR, aggregate accuracy scores, or report dollar-value ROI. Time saved is reported in minutes, not converted into currency.

Feedback (Slack Thumbs)​

Team members give feedback directly in Slack: each investigation message carries per-section thumbs up / thumbs down controls so engineers can rate parts of an investigation in context. This feedback lives in Slack and is not aggregated into a portal accuracy metric. Use it as qualitative signal on where investigations are most and least useful.

Reporting to Leadership​

For a status update, the Dashboard gives you concrete, defensible numbers without overstating them:

  • Alert volume and how much of it OpsWorker handled.
  • Count of finished investigations over the period.
  • Total time saved in minutes, which you can translate into team capacity in whatever way your organization prefers.

Outcome​

  • Honest metrics: alerts by status, finished investigations, and time saved in minutes, no invented MTTR or ROI.
  • Qualitative feedback: per-section thumbs in Slack show where investigations land well.
  • Leadership-ready: concrete counts and minutes saved, filterable by cluster and date range.