Prometheus Exposition — Summary with and without Quantiles (prom)
Two summary families — one exposing four client-side quantiles including quantile="1" for the observed maximum, and one exposing only _sum and _count, which is legal and common. Summaries cannot be re-aggregated across instances, and this fixture is where that gets tested.
# HELP rpc_duration_seconds Payment RPC latency summary.
# TYPE rpc_duration_seconds summary
rpc_duration_seconds{service="payments-api",quantile="0.5"} 0.0412
rpc_duration_seconds{service="payments-api",quantile="0.9"} 0.1188
rpc_duration_seconds{service="payments-api",quantile="0.99"} 0.4907
rpc_duration_seconds{service="payments-api",quantile="1"} 2.0031
rpc_duration_seconds_sum{service="payments-api"} 918.4471
rpc_duration_seconds_count{service="payments-api"} 14022
# HELP gc_pause_seconds Garbage-collection pause summary with no quantiles configured.
# TYPE gc_pause_seconds summary
gc_pause_seconds_sum{service="checkout-api"} 41.2208
gc_pause_seconds_count{service="checkout-api"} 90311
Specifications
- Families
- 2
- Quantiles
- 4
- Quantile One Is Max
- true
- Family Without Quantiles
- gc_pause_seconds
- Count
- 14022
Testing contract
Expected to pass- Scenario
- Parse both families and attempt to aggregate them across instances.
- Expected result
- The quantile label is recognised as part of the series identity rather than a bucket bound, and the quantile-free family still yields a valid average from _sum divided by _count.
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
“Prometheus Exposition — Summary with and without Quantiles (prom)” is a deterministic Novus Examples fixture for Observability, Time-series data, Time-series data. 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 · 700 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
- 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.
- 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.
- promOpenMetrics — 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.
- promOpenMetrics — Histogram Exemplars Linking to the Trace Fixtures (prom)Histogram buckets carrying exemplars whose trace_id and span_id resolve against the OTLP trace fixtures in this category — the exact-to-example link that turns a latency spike on a graph into a specific request. Five exemplars, each with its own observed value and timestamp.
- jsonOTLP Metrics — Base-2 Exponential Histogram (json)An exponential histogram at scale 3 — eight buckets per power of two — with a negative offset, a zero bucket and its threshold. Bucket i covers (base^(offset+i), base^(offset+i+1)], and getting that indexing wrong silently shifts every percentile, which is what this fixture is for.
Generated by generation/observability.py. Free for any use, no attribution required — license.