incident_impact_observed: from owned boundary to trusted query
Treat incident_impact_observed as a durable analytical contract: the owner emits one documented grain, a fixture proves the fields, and a reviewed query answers the stated question.
- 1
Outcome becomes final
Affected service or incident enrichment pipeline emits only when an operation falls inside a confirmed impact rule.
- 2
Contract is bounded
9 required fields preserve the declared grain: One affected operation associated with a declared incident.
- 3
Fixture is verified
Check types, UTC time, alternate outcomes, idempotency, and every pseudonymous or review-classified field.
- 4
Question is answered
Which accounts and workflows were affected during an incident?
Grain
One affected operation associated with a declared incident.
Owner
Affected service or incident enrichment pipeline
Emit when
When an operation falls inside a confirmed impact rule.
Field contract
Typed fields with explicit privacy boundaries
Keep existing field names and types stable after production queries depend on them. Optional context should remain bounded, documented, and justified by a specific decision.
| Field | Type | Required | Privacy | Meaning |
|---|---|---|---|---|
| timestamp_utc | timestamp | yes | non-sensitive | UTC time at the outcome boundary. |
| event_id | string | yes | non-sensitive | Stable unique identifier used for deduplication. |
| release | string | yes | non-sensitive | Application or service version that emitted the event. |
| account_id | string | yes | pseudonymous | Stable internal account identifier, never an email or name. |
| incident_id | string | yes | non-sensitive | Stable declared incident identifier. |
| service | string | yes | non-sensitive | Affected service. |
| workflow | string | yes | non-sensitive | Affected customer workflow. |
| region | string | yes | non-sensitive | Coarse region for impact grouping. |
| impact_type | string | yes | non-sensitive | Low-cardinality symptom such as timeout or elevated latency. |
Synthetic JSON event
{
"timestamp_utc": "2026-07-28T14:31:40Z",
"event_id": "evt_impact_01",
"account_id": "acct_8f31",
"release": "2026.07.2",
"incident_id": "inc_checkout_latency",
"service": "checkout",
"workflow": "subscription_upgrade",
"region": "north_america",
"impact_type": "upstream_timeout"
}Privacy review
Review identifiers before ingestion
This example uses synthetic identifiers. Pseudonymous values can still be personal data, and review fields can expose business or provider context. Apply your own consent, retention, access, residency, and deletion requirements.
account_id: pseudonymous
Validation checklist
Prove the contract before building a dashboard
- Send one known incident_impact_observed fixture after the documented outcome boundary.
- Verify all 9 required fields arrive with the documented types.
- Retry the same event identifier and confirm the chosen deduplication behavior.
- Send a controlled failure or alternate outcome when the workflow supports one.
- Run the related SQL over a fixed window and reconcile the result to the fixture.
Common mistakes
Keep one row equal to one durable outcome
- Emitting incident_impact_observed before affected service or incident enrichment pipeline knows the final outcome.
- Mixing several grains in one table, which makes counts and rates ambiguous.
- Replacing controlled categories with raw URLs, payloads, prompts, or error text.
- Changing a field type in place after saved queries and dashboards depend on it.
- Adding identifiers without a documented investigation, access, and retention need.
Use the contract
Query and operationalize the event
Related contracts
Send a fixture before production traffic
Create a free API key, send the synthetic event, and inspect the inferred table before connecting a live workflow.