Add 7 Grafana dashboards to close T17 observability gap#70
Merged
Conversation
…g T17 audit gap Agent-Logs-Url: https://github.com/unnamedlab/OpenFoundry/sessions/da69e7eb-5294-4f0f-8243-6eb251188a0d Co-authored-by: unnamedlab <272794385+unnamedlab@users.noreply.github.com>
Copilot created this pull request from a session on behalf of
unnamedlab
April 30, 2026 09:35
View session
unnamedlab
pushed a commit
that referenced
this pull request
May 18, 2026
…-3-aggregate feat(pipeline-build-service): promote aggregate to available (ADR-0045 Phase C.3)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The audit flagged that
infra/observability/grafana-dashboards/shipped only 3 JSON dashboards (dp-slo-overview,dp-slo-datafusion,dp-slo-nats) whileinfra/observability/prometheus-rules/defined alerts for 7 components — leaving on-call without panels for Kafka, ClickHouse, CNPG, Vespa, Lakekeeper and Flink.Per-SLO dashboards (ADR-0012 §2)
Generated from the existing
dp-slo-nats.jsontemplate, substituting metric, selector, latency bound (le), SLO target (99.5 %) and the multi-window page thresholds (1h × 14.4 = 0.072, 6h × 6 = 0.030 of budget):dp-slo-flightsql.json— §2.1,flight_sql_query_duration_seconds,le="0.020"dp-slo-kafka.json— §2.3,kafka_producer_request_latency_seconds,le="0.025"dp-slo-clickhouse.json— §2.4,clickhouse_query_duration_seconds,le="0.200"dp-slo-vespa.json— §2.5,vespa_query_latency_seconds,le="0.080"Each dashboard ships the same 9-panel layout as the NATS one: p50/p99/p99.9 stats, 30-day compliance, request rate, latency timeseries with the SLO line, 1h-vs-6h burn-rate with both page thresholds drawn, and budget remaining.
Operator / fleet overviews
Panelling the exact series the existing PrometheusRules already alert on — no new metrics introduced:
lakekeeper-overview.json— RED (http_requests_total,http_request_duration_seconds_bucket) + sqlx pool saturation; mirrorslakekeeper.yaml.cnpg-overview.json— fleet view across the per-bounded-context clusters ininfra/k8s/cnpg/clusters/: primaries reachable, max replica lag with the 1 GiB threshold, switchover events, WAL-archiver failures.flink-overview.json—flink_jobmanager_job_uptime, failed checkpoints over 30 m, time since last checkpoint vs the 1 h alert line, latest savepoint age vs the 24 h T15 maintenance line.README
infra/observability/grafana-dashboards/README.md: per-SLO inventory flipped from TBD → shipped; the per-component table now lists the three OpenFoundry-specific overviews alongside the upstream-preferred entries (rationale for keeping the rest on grafana.com/IDs is preserved).All 10 JSONs declare
__inputs[].name = DS_PROMETHEUSso they import unmodified into any Grafana with a Prometheus datasource.