ANALYTICS
Use incident and service performance data to understand response times, trends and SLA outcomes.
WHAT IT SOLVES
Explore incident volume, acknowledgement and resolution timing with the available dashboard filters. Compare like-for-like time windows and service context.
Understand the capability
HOW IT WORKS
EXPLORE A WORKFLOW
Timing metrics only make sense with the selected incident population and time window visible. Use them to identify a pattern, not to infer root cause automatically.
OPERATIONAL DEPTH
The details below are the parts teams need when evaluating how the capability behaves during real response, failure, and handoff.
An active incident count describes the current response. MTTA and MTTR describe timing across the selected population; inspect the sample and filters before drawing conclusions.
Read the operational guideUse the analysis to identify repeated incidents and response bottlenecks, then connect findings to owned postmortem action items. Metrics support investigation rather than explaining root cause on their own.
Read the operational guideRecord the selected time range and service scope when sharing a finding. Follow the analytics guide to understand available views and operational limitations.
Read the operational guideKNOW BEFORE PRODUCTION
Use a test service and representative provider configuration before treating analytics as production incident infrastructure.
Run OpsKnight on infrastructure you control.
v2.0.0 · AGPL-3.0-only · Self-hosted · 28 inbound integrations
OpsKnight