Engineering Incident Metrics Operational

Incident Count

Incident Count: Number of incidents in a period.

Formula

Incident Count = Total incidents reported

Computable definition

The canonical formula in the GASP formula grammar. The MCP server compiles it to SQL over the datasets listed below.

count_distinct(field.incident_id)

Unit: count

Breakdowns

by_severity: one row per severity value
by_incident_type: one row per incident_type value

Notes: by_severity returns one row per severity (sev1 to sev4), because a month of sev4 noise and a month with one sev1 outage call for different responses. by_incident_type splits availability, performance, security and data incidents, which have different owners.

Data requirements

Grain: Per event · Frequency: Per incident · Aggregation: event · Staged: no · Main source: Incident Management.

Field	Dataset	Type
`incident_id`	incident	string
`started_at`	incident	timestamp

Example SQL (Postgres)

SELECT (SELECT COUNT(DISTINCT incident_id) FROM incident WHERE started_at >= :period_start AND started_at < (:period_end + INTERVAL '1 day')) AS incident_count

From an agent: with the GASP MCP server, call lookup_metric({ "name": "Incident Count" }) or generate_query({ "metric": "Incident Count", "adapter": "<your adapter JSON>" }).

What It Tells You

System stability. Read the trend per severity, since one SEV1 outweighs a month of SEV4 noise.

← Back to Engineering metrics