Prometheus HTTP API — Instant Query Vector with Warnings (json)
An instant-query response: five up series at a single evaluation timestamp, one of them zero, plus a warnings array that clients routinely ignore. A successful response can carry warnings, and dropping them hides truncated results.
{
"status": "success",
"data": {
"resultType": "vector",
"result": [
{
"metric": {
"__name__": "up",
"job": "checkout-api",
"instance": "192.0.2.11:9090"
},
"value": [
1773738872,
"1"
]
},
{
"metric": {
"__name__": "up",
"job": "cart-api",
"instance": "192.0.2.12:9090"
},
"value": [
1773738872,
"1"
]
},
{
"metric": {
"__name__": "up",
"job": "inventory-api",
"instance": "192.0.2.21:9090"
},
"value": [
1773738872,
"1"
]
},
{
"metric": {
"__name__": "up",
"job": "payments-api",
"instance": "192.0.2.22:9090"
},
"value": [
1773738872,
"1"
]
},
{Specifications
- Result Type
- vector
- Series
- 5
- Down Targets
- 1
- Has Warnings
- true
- Evaluation Timestamp
- 1773738872
Testing contract
Expected to pass- Scenario
- Parse the response and surface both the samples and the warnings.
- Expected result
- Five vector samples parse with one zero-valued target, and the warnings array is surfaced rather than discarded because status is success.
What is a .json file?
JSON (JavaScript Object Notation) is a lightweight, text-based data-interchange format representing objects, arrays, strings, numbers, booleans, and null. It is language-independent, human-readable, and the dominant format for web APIs and configuration. It requires a single well-formed root value.
How to use this file
Use an example JSON file to test parsers and serializers, schema validation, Unicode and number-precision handling, and API request or response processing.
How to use this file for testing
“Prometheus HTTP API — Instant Query Vector with Warnings (json)” is a deterministic Novus Examples fixture for Observability, JSON parsing, API testing. 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: JSON · 1,244 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("prometheus-api-query-instant.json") as f:
data = json.load(f)
print(type(data), len(data))Related files
- jsonAlertmanager Webhook — Firing Notification (json)The JSON body Alertmanager POSTs to a webhook when an alert fires, including the detail that catches everyone: endsAt is Go's zero time rather than null or absent, so a receiver that parses it as a real timestamp records an alert that ended in the year 1.
- jsonAlertmanager Webhook — Grouped Batch with Truncation (json)One notification carrying twelve grouped alerts with truncatedAlerts set to 8, meaning twenty were firing. Receivers that count the alerts array report a smaller incident than actually exists — the field is there precisely so that does not have to happen.
- jsonAlertmanager Webhook — Resolved Notification (json)The resolved notification for the same alert half an hour later, carrying an identical fingerprint and group key with endsAt now populated. Paired with the firing payload so incident-tracking code can be tested for correctly closing the incident it opened.
- 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.
- 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.