OpenMetrics — Full Document with UNIT, info and stateset (prom)
A complete OpenMetrics document — the _total and _created series a counter really has, UNIT metadata, an info metric carrying build metadata and a stateset with exactly one active state — terminated by the mandatory # EOF. This is what the exposition format became once it was standardised.
# TYPE shop_orders counter
# HELP shop_orders Orders accepted since process start.
shop_orders_total{service="checkout-api"} 24518
shop_orders_created{service="checkout-api"} 1773652472.0
# TYPE http_request_duration_seconds histogram
# UNIT http_request_duration_seconds seconds
# HELP http_request_duration_seconds End-to-end request latency.
http_request_duration_seconds_bucket{service="checkout-api",le="0.005"} 12
http_request_duration_seconds_bucket{service="checkout-api",le="0.01"} 341
http_request_duration_seconds_bucket{service="checkout-api",le="0.025"} 2210
http_request_duration_seconds_bucket{service="checkout-api",le="0.05"} 7412
http_request_duration_seconds_bucket{service="checkout-api",le="0.1"} 15908
http_request_duration_seconds_bucket{service="checkout-api",le="0.25"} 21744
http_request_duration_seconds_bucket{service="checkout-api",le="0.5"} 23511
http_request_duration_seconds_bucket{service="checkout-api",le="1.0"} 24102
http_request_duration_seconds_bucket{service="checkout-api",le="2.5"} 24398
http_request_duration_seconds_bucket{service="checkout-api",le="5.0"} 24487
http_request_duration_seconds_bucket{service="checkout-api",le="10.0"} 24512
http_request_duration_seconds_bucket{service="checkout-api",le="+Inf"} 24518
http_request_duration_seconds_count{service="checkout-api"} 24518
http_request_duration_seconds_sum{service="checkout-api"} 3418.2214
http_request_duration_seconds_created{service="checkout-api"} 1773652472.0
# TYPE process_resident_memory_bytes gauge
# UNIT process_resident_memory_bytes bytes
# HELP process_resident_memory_bytes Resident memory size.
process_resident_memory_bytes{service="checkout-api"} 418709504
# TYPE build info
# HELP build Build metadata as an info metric, always valued 1.
build_info{service="checkout-api",version="1.14.2",revision="9f31a7c"} 1
# TYPE deployment_state stateset
# HELP deployment_state Mutually exclusive deployment states.
deployment_state{service="checkout-api",deployment_state="rolling"} 0
deployment_state{service="checkout-api",deployment_state="stable"} 1
deployment_state{service="checkout-api",deployment_state="failed"} 0
# EOF
Specifications
- Dialect
- OpenMetrics 1.0
- Families
- 5
- Has Eof
- true
- Has Unit Metadata
- true
- Has Created Series
- true
- Metric Types
- counter, histogram, gauge, info, stateset
Testing contract
Expected to pass- Scenario
- Parse the document with an OpenMetrics parser and enumerate its metric types.
- Expected result
- Five families parse including the info and stateset types Prometheus text has no way to express, the # EOF marker is consumed, and exactly one deployment_state series has value 1.
What is a .prom file?
A .prom file holds metrics in the Prometheus text exposition format, the same body a `/metrics` endpoint returns. Each metric family is introduced by `# HELP` and `# TYPE` comments and followed by one sample per line: a metric name, an optional brace-delimited label set, a value, and an optional millisecond timestamp. Counters, gauges, histograms (with `_bucket`, `_sum`, `_count` series and a `+Inf` bucket), and summaries with quantile labels all use this one grammar.
How to use this file
Use an example .prom file to test exposition-format parsers, scrapers, and the node_exporter textfile collector — checking label escaping, histogram bucket ordering and cumulative counts, and the handling of `NaN` and `+Inf` values.
How to use this file for testing
“OpenMetrics — Full Document with UNIT, info and stateset (prom)” is a deterministic Novus Examples fixture for Observability, Time-series data, Schema validation. 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: PROM · 2,141 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.
Related files
- csvMetric Range Export — Long (Tidy) CSV (csv)The same 90 samples as the query_range response, exported one row per observation with both epoch and ISO 8601 timestamps. The long layout every dataframe library prefers, and half of a reshaping pair.
- csvMetric Range Export — Wide (Pivoted) CSV (csv)The same 90 samples pivoted to one column per service and one row per timestamp — the layout a spreadsheet chart expects. Paired with the long-format export so a reshape can be scored in both directions.
- jsonOTLP Metrics — Counter Reset on Process Restart (json)A monotonic counter that drops from 94,880 to 1,120 when its process restarts, with startTimeUnixNano changing at exactly that point to mark the reset. Rate calculations that subtract consecutive values without checking the start timestamp produce a large negative rate here.
- jsonOTLP Metrics — Cumulative Temporality (json)Cumulative sums whose start timestamp stays fixed across exports, so every point is the running total since process start. Paired with a delta-temporality twin covering the same window, because converting between the two is a stateful operation that a bridge must get right in both directions.
- jsonOTLP Metrics — Delta Temporality (json)The same 24 hours of cart updates as six delta points, each with its own start and end timestamp covering a four-hour window. The delta twin of the cumulative fixture: summing these must reproduce the cumulative total exactly, and a gap or overlap in the windows is the failure to catch.
- jsonOTLP Metrics — Exemplars with Trace and Span IDs (json)An OTLP histogram carrying two exemplars, each with the trace and span ID of a request that landed in that bucket — including the 2.0031-second outlier that corresponds to the failed payment in the error-trace fixture. The metrics-to-traces jump, with a resolvable target.
Generated by generation/observability.py. Free for any use, no attribution required — license.