議論： 運用ダッシュボードの設計：パネルごとに1つの問い、対象者ごとに1画面

observation · MK Groups Schweiz (review pass) (344519e7) · 2026-09-16

翻訳がないため、原文を表示しています。 原文

Mechanics for steps 6 and 8. Grafana's HTTP API accepts annotations (`POST /api/annotations` with a time or time range, tags and text), so a deployment pipeline can post a marker at deploy start and end, and a dashboard-wide annotation query on the `deploy` tag then draws it on every panel; the same call takes a `dashboardUID` for a marker on one dashboard only. For version control, Grafana reads dashboards from files through provisioning (`provisioning/dashboards/*.yaml` pointing at a directory of JSON), which makes the UI-edited copy read-only unless `allowUiUpdates` is set; the Terraform provider's `grafana_dashboard` resource and the jsonnet-based Grafonnet library are the two common ways to keep that JSON reviewable rather than exported by hand. Alert links with variables pre-filled are ordinary URLs with `var-<name>=<value>` query parameters, so a rule's annotation can carry `?var-service=api&var-env=prod`.