Alert State History — Pending, Firing and Resolved Transitions (jsonl)
Sixteen state transitions across four alerts, each moving inactive to pending to firing to resolved with the previous state recorded. The pending stage is where a for: duration is being served and no notification is sent, which is what makes alert-noise analysis possible.
{"ts":"2026-03-17T09:14:32.850Z","alertname":"CheckoutLatencySLOBurn","state":"pending","previous_state":"inactive","service":"checkout-api","severity":"critical","fingerprint":"9f31a7c4e6b84f1d","value":1.0,"receiver":"platform-oncall","notification_sent":false}
{"ts":"2026-03-17T09:19:32.850Z","alertname":"CheckoutLatencySLOBurn","state":"firing","previous_state":"pending","service":"checkout-api","severity":"critical","fingerprint":"9f31a7c4e6b84f1d","value":1.03,"receiver":"platform-oncall","notification_sent":true}
{"ts":"2026-03-17T09:29:32.850Z","alertname":"CheckoutLatencySLOBurn","state":"firing","previous_state":"pending","service":"checkout-api","severity":"critical","fingerprint":"9f31a7c4e6b84f1d","value":1.09,"receiver":"platform-oncall","notification_sent":true}
{"ts":"2026-03-17T09:44:32.850Z","alertname":"CheckoutLatencySLOBurn","state":"resolved","previous_state":"firing","service":"checkout-api","severity":"critical","fingerprint":"9f31a7c4e6b84f1d","value":1.18,"receiver":"platform-oncall","notification_sent":true}
{"ts":"2026-03-17T10:14:32.850Z","alertname":"HighErrorRate","state":"pending","previous_state":"inactive","service":"cart-api","severity":"warning","fingerprint":"9f31a7c4e6b84f1e","value":1.37,"receiver":"shop-team","notification_sent":false}
{"ts":"2026-03-17T10:19:32.850Z","alertname":"HighErrorRate","state":"firing","previous_state":"pending","service":"cart-api","severity":"warning","fingerprint":"9f31a7c4e6b84f1e","value":1.4,"receiver":"shop-team","notification_sent":true}
{"ts":"2026-03-17T10:29:32.850Z","alertname":"HighErrorRate","state":"firing","previous_state":"pending","service":"cart-api","severity":"warning","fingerprint":"9f31a7c4e6b84f1e","value":1.46,"receiver":"shop-team","notification_sent":true}
{"ts":"2026-03-17T10:44:32.850Z","alertname":"HighErrorRate","state":"resolved","previous_state":"firing","service":"cart-api","severity":"warning","fingerprint":"9f31a7c4e6b84f1e","value":1.55,"receiver":"shop-team","notification_sent":true}
{"ts":"2026-03-17T11:14:32.850Z","alertname":"TargetDown","state":"pending","previous_state":"inactive","service":"inventory-api","severity":"critical","fingerprint":"9f31a7c4e6b84f1f","value":1.74,"receiver":"platform-oncall","notification_sent":false}
{"ts":"2026-03-17T11:19:32.850Z","alertname":"TargetDown","state":"firing","previous_state":"pending","service":"inventory-api","severity":"critical","fingerprint":"9f31a7c4e6b84f1f","value":1.77,"receiver":"platform-oncall","notification_sent":true}
{"ts":"2026-03-17T11:29:32.850Z","alertname":"TargetDown","state":"firing","previous_state":"pending","service":"inventory-api","severity":"critical","fingerprint":"9f31a7c4e6b84f1f","value":1.83,"receiver":"platform-oncall","notification_sent":true}
{"ts":"2026-03-17T11:44:32.850Z","alertname":"TargetDown","state":"resolved","previous_state":"firing","service":"inventory-api","severity":"critical","fingerprint":"9f31a7c4e6b84f1f","value":1.92,"receiver":"platform-oncall","notification_sent":true}
{"ts":"2026-03-17T12:14:32.850Z","alertname":"BackupTooOld","state":"pending","previous_state":"inactive","service":"payments-api","severity":"warning","fingerprint":"9f31a7c4e6b84f20","value":2.11,"receiver":"shop-team","notification_sent":false}
{"ts":"2026-03-17T12:19:32.850Z","alertname":"BackupTooOld","state":"firing","previous_state":"pending","service":"payments-api","severity":"warning","fingerprint":"9f31a7c4e6b84f20","value":2.14,"receiver":"shop-team","notification_sent":true}
{"ts":"2026-03-17T12:29:32.850Z","alertname":"BackupTooOld","state":"firing","previous_state":"pending","service":"payments-api","severity":"warning","fingerprint":"9f31a7c4e6b84f20","value":2.2,"receiver":"shop-team","notification_sent":true}
{"ts":"2026-03-17T12:44:32.850Z","alertname":"BackupTooOld","state":"resolved","previous_state":"firing","service":"payments-api","severity":"warning","fingerprint":"9f31a7c4e6b84f20","value":2.29,"receiver":"shop-team","notification_sent":true}
Specifications
- Lines
- 16
- Alerts
- 4
- States Per Alert
- 4
- States
- pending, firing, resolved
- Notifications Sent
- 12
- Has Previous State
- true
- Has Fingerprint
- true
Testing contract
Expected to pass- Scenario
- Reconstruct each alert's lifetime from the transition stream.
- Expected result
- Four alerts each reconstruct to a 30-minute firing period, notifications are counted only for firing and resolved transitions, and the pending states are excluded from mean-time-to-acknowledge.
What is a .jsonl file?
JSONL (JSON Lines) is a text format where each line is a complete, independent JSON value, allowing records to be streamed and appended without parsing the whole file. It is not itself a JSON array and each line must stand alone. It is common in logging, machine learning datasets, and data pipelines.
How to use this file
Use an example JSONL to test line-by-line streaming parsers, append-and-resume ingestion, and batch pipelines that process one record per line.
How to use this file for testing
“Alert State History — Pending, Firing and Resolved Transitions (jsonl)” is a deterministic Novus Examples fixture for Observability, Log parsing, JSON parsing. Structured and plain-text telemetry with known timestamps, levels, request identifiers, and error states for testing log ingestion, correlation, dashboards, and alert pipelines.
Documented properties for this file: JSONL · 4,013 bytes. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.
Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such — expect parsers to fail loudly rather than silently accept them.
Telemetry fixtures use fixed trace IDs, span IDs, and timestamps so ingestion is reproducible run to run. Point your collector, parser, or query layer at the file and assert the documented span tree, metric families, or severity mix; service and host names are invented.
Code examples
import json
with open("alert-state-history.jsonl") as f:
rows = [json.loads(line) for line in f]
print(len(rows), rows[0])Related files
- jsonlEnvoy-Style Proxy Access Log — JSON Lines (jsonl)Forty service-mesh proxy access records with the fields that make mesh debugging possible: response_flags distinguishing an upstream failure from an overflow, upstream_service_time against total duration, upstream host and cluster, and a request ID for correlation.
- jsonlKubernetes Audit Log — Six Events with an RBAC Denial (jsonl)Six Kubernetes audit events at two audit levels, including one 403 whose authorization annotations record the forbid decision and its reason. The shape a cluster-audit alert or compliance report reads, with every user and service account invented.
- jsonOTLP Logs — Export Document with Severity and Trace Correlation (json)An OTLP logs export across two resources: five records spanning DEBUG to FATAL with both severityNumber and severityText, separate event and observed timestamps, trace and span correlation, and one record whose body is a full multi-line Python traceback.
- jsonlStructured Application Log — 300 JSON Lines (jsonl)Three hundred newline-delimited JSON log records from five services, each with a timestamp, level, logger, message, a nested http object and request and order identifiers. The severity mix is counted in the spec table, so a level filter can be asserted rather than eyeballed.
- jsonlStructured Log — Deeply Nested and Very Wide Context (jsonl)One record nested 24 levels deep, one with 200 sibling keys and one holding a 12 by 12 array of arrays. Field-flattening pipelines turn these into hundreds of dotted keys, and depth limits truncate them silently — this is where both behaviours become visible.
- jsonlStructured Log — Duplicate Keys in One JSON Object (jsonl)Records whose objects declare the same key twice, including one where the duplicate changes the severity from debug to error. RFC 8259 permits duplicate names and leaves the outcome undefined, so last-wins and first-wins parsers disagree about what these records say.
Generated by generation/observability.py. Free for any use, no attribution required — license.