Dashboard JSON — Chained Template Variables (json)
A dashboard driven by four template variables, one of which queries using the value of another — the chained dependency that must be resolved in order. Multi-select variables interpolate as regex alternations, which is why every query here uses =~ rather than =.
{
"uid": "shop-service-drilldown",
"title": "Shop — Service Drilldown",
"tags": [
"shop",
"generated-fixture"
],
"schemaVersion": 39,
"version": 1,
"editable": true,
"time": {
"from": "now-1h",
"to": "now"
},
"templating": {
"list": [
{
"name": "service",
"type": "query",
"label": "Service",
"datasource": {
"type": "prometheus",
"uid": "shop-prometheus"
},
"query": "label_values(up, job)",
"refresh": 1,
"multi": true,
"includeAll": true,
"allValue": ".*",
"current": {
"text": [
"All"
],
"value": [
"$__all"
]
}
},
{
"name": "route",
"type": "query",
"label": "Route",
"datasource": {
"type": "prometheus",
"uid": "shop-prometheus"
},
"query": "label_values(http_requests_total{service=~\"$service\"}, route)",
"refresh": 2,
"multi": true,
"includeAll": trueSpecifications
- Panels
- 2
- Variables
- 4
- Variable Types
- query, query, interval, custom
- Chained Variables
- 1
- Multi Select Variables
- 2
- All Value Regex
- .*
- Schema Version
- 39
Testing contract
Expected to pass- Scenario
- Resolve the variables in dependency order and interpolate the panel queries.
- Expected result
- route resolves only after service, multi-select values interpolate as a regex alternation compatible with the =~ matchers, and $__all expands to the .* allValue.
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
“Dashboard JSON — Chained Template Variables (json)” is a deterministic Novus Examples fixture for Observability, JSON parsing, Config 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 · 3,103 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("grafana-dashboard-templated.json") as f:
data = json.load(f)
print(type(data), len(data))Related files
- jsonOTLP Trace — Head and Tail Sampling Attributes (json)A trace annotated with the sampling decision that let it through — sampler type and ratio on every span, plus a sampling.priority override on the root. The fixture for testing that a tail-sampling processor reads the existing decision instead of re-deciding and splitting the trace.
- jsonlAlert 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.
- yamlAlertmanager Config — Routing Tree, Inhibition and Mute Windows (yaml)An Alertmanager configuration with the routing behaviour that is hard to reason about without a fixture: a continue: true branch so a critical alert reaches two receivers, an inhibition rule suppressing warnings under a matching critical, and a weekend mute window.
- 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.
Generated by generation/observability.py. Free for any use, no attribution required — license.