You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 8, 2026. It is now read-only.
Part of: Prometheus Monitoring Implementation (Phase 4 - Grafana Dashboards) Parent Issue:#1062 Priority: Low Effort: S
Description
Capture screenshots of each of the 4 Grafana dashboards for use in documentation. This requires a running Grafana instance with a Prometheus datasource populated with runner metrics data.
Dashboards to Screenshot
Dashboard
File
UID
Runner Overview
runner-overview.json
github-runner-runner-overview
DORA Metrics
dora-metrics.json
github-runner-dora
Performance Trends
performance-trends.json
github-runner-performance
Job Analysis
job-analysis.json
github-runner-job-analysis
Acceptance Criteria
Screenshot captured for each of the 4 dashboards showing panels with sample data
Screenshots saved to docs/images/ or equivalent directory
Screenshots referenced in docs/features/GRAFANA_DASHBOARD_METRICS.md
Images optimized for web (compressed PNG or WebP)
Prerequisites
Running Grafana instance (v9.0+) with Prometheus datasource
At least one runner generating metrics data for realistic panel content
All 4 dashboard JSON files imported into Grafana
Notes
This was deferred during Phase 4 implementation because it requires a live environment with real metrics data. Can be completed when a monitoring stack is available for testing.
TASK-044: Capture Dashboard Screenshots
Part of: Prometheus Monitoring Implementation (Phase 4 - Grafana Dashboards)
Parent Issue: #1062
Priority: Low
Effort: S
Description
Capture screenshots of each of the 4 Grafana dashboards for use in documentation. This requires a running Grafana instance with a Prometheus datasource populated with runner metrics data.
Dashboards to Screenshot
Acceptance Criteria
Prerequisites
Notes
This was deferred during Phase 4 implementation because it requires a live environment with real metrics data. Can be completed when a monitoring stack is available for testing.