Part of #5365.
Context: Sentry (sentry.io, self-hoster's own project) is currently only reachable from Grafana via a plain hyperlink in resource-hub.json's "Observability & dashboards" panel. There is no way to see Sentry error/issue data alongside the rest of the stack's metrics/logs/traces in Grafana itself. This is distinct from #5007 (Sentry+Alertmanager notification/alerting consolidation) — this issue is about visualization/analysis, not paging.
Requirements:
- Research current Grafana Sentry datasource plugin availability/support level (verify the plugin still exists and is compatible with this repo's pinned Grafana version,
grafana/grafana:13.1.0) — do not assume a specific plugin name/version without checking, since plugin ecosystems shift.
- If a suitable plugin exists: mirror the exact established pattern this repo already uses for
grafana-github-datasource (see scripts/setup-github-datasource.sh) — API-based post-boot provisioning (not file-provisioning, since it needs a token/DSN not available at Grafana boot time), a new scripts/setup-sentry-datasource.sh using a Sentry API auth token + org/project slug (note: SENTRY_DSN alone is not sufficient for a query-capable API integration; a proper auth token with project:read/event:read scope is needed — document this clearly, since it's a different credential than the DSN this repo already uses for error reporting).
- Add relevant dashboard panels (recent issues by level, issue volume trend, top issues by event count) — either a new dedicated dashboard or a section of an existing one.
- Document the setup in the self-hosting docs (mirroring how the GitHub datasource setup is documented) and update
resource-hub.json's markdown to point at the new in-Grafana view instead of (or alongside) the plain external link.
- If no viable plugin exists (verify before ruling this out): fall back to documenting this as a known gap rather than building custom Sentry-API-polling infrastructure from scratch, similar to how Ollama's lack of a metrics endpoint is being handled in the parent epic.
Deliverables:
- Either: a working Sentry Grafana datasource + setup script + dashboard panels + docs, OR a documented, verified conclusion that this isn't currently feasible without disproportionate custom infrastructure.
- Tests mirroring the existing GitHub-datasource setup script's test coverage, if the plugin path is taken.
Expected outcomes: A self-hoster can see recent Sentry errors/issues directly in a Grafana panel, correlated in time with the rest of their stack's metrics/logs/traces, without leaving Grafana — or, if not currently feasible, a clear documented reason why not.
Links/resources:
Part of #5365.
Context: Sentry (sentry.io, self-hoster's own project) is currently only reachable from Grafana via a plain hyperlink in
resource-hub.json's "Observability & dashboards" panel. There is no way to see Sentry error/issue data alongside the rest of the stack's metrics/logs/traces in Grafana itself. This is distinct from #5007 (Sentry+Alertmanager notification/alerting consolidation) — this issue is about visualization/analysis, not paging.Requirements:
grafana/grafana:13.1.0) — do not assume a specific plugin name/version without checking, since plugin ecosystems shift.grafana-github-datasource(seescripts/setup-github-datasource.sh) — API-based post-boot provisioning (not file-provisioning, since it needs a token/DSN not available at Grafana boot time), a newscripts/setup-sentry-datasource.shusing a Sentry API auth token + org/project slug (note:SENTRY_DSNalone is not sufficient for a query-capable API integration; a proper auth token withproject:read/event:readscope is needed — document this clearly, since it's a different credential than the DSN this repo already uses for error reporting).resource-hub.json's markdown to point at the new in-Grafana view instead of (or alongside) the plain external link.Deliverables:
Expected outcomes: A self-hoster can see recent Sentry errors/issues directly in a Grafana panel, correlated in time with the rest of their stack's metrics/logs/traces, without leaving Grafana — or, if not currently feasible, a clear documented reason why not.
Links/resources:
scripts/setup-github-datasource.sh— the exact pattern to mirror for an API-token-gated, post-boot-provisioned datasource.grafana/dashboards/resource-hub.json— where the current plain Sentry link lives today.