chore(selfhost): remove the dead Grafana Sentry-datasource dashboard#8712
Merged
Conversation
Self-host stopped sending new events to Sentry once PostHog error tracking replaced it (epic #8286). This in-Grafana Sentry issue-visualization panel only ever showed the app's own Sentry history, so it's now permanently empty for any new deployment -- removes the grafana-sentry-datasource plugin, its dashboard, setup script, docs section, and .env.example block, and fixes a stale docs-audit note that still said source maps upload to Sentry (they upload to PostHog now). Also fixes the resource-hub.json external Sentry link's stale pre-rename project slug (gittensory -> loopover). The release-pipeline @sentry/cli references were already fully removed in tonight's earlier PostHog migration work -- nothing left there.
Contributor
|
Superagent didn't find any vulnerabilities or security issues in this PR. |
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
loopover-ui | dd0230a | Commit Preview URL Branch Preview URL |
Jul 26 2026, 12:21 AM |
Bundle ReportChanges will decrease total bundle size by 5.05kB (-0.07%) ⬇️. This is within the configured threshold ✅ Detailed changes
Affected Assets, Files, and Routes:view changes for bundle: loopover-uiAssets Changed:
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #8712 +/- ##
=======================================
Coverage 93.79% 93.79%
=======================================
Files 797 797
Lines 79480 79480
Branches 24078 24078
=======================================
Hits 74545 74545
Misses 3563 3563
Partials 1372 1372
Flags with carried forward coverage won't be shown. Click here to find out more. |
loopover-orb
Bot
added
the
gittensor:bug
Contributor
|
Warning ⏸️ LoopOver review result - manual review recommendedReview updated: 2026-07-26 00:35:56 UTC
Review summary Nits — 2 non-blocking
Concerns raised — review before merging
📋 Copy for AI agents — paste into your coding agentDecision drivers
Context & advisory signals — never blocks the verdict
Review context
Contributor next steps
Signal definitions
🧪 Chat with LoopOverAsk LoopOver a question about this PR directly in a comment — grounded only in the same cached, public-safe facts shown above, never a new claim.
Full command reference: https://loopover.ai/docs/loopover-commands 🧪 Experimental — new and may change. Visual preview
Click any thumbnail to open the full-size screenshot. Before = production · After = this PR's preview deploy. Scroll preview
A short scroll-through clip (desktop) — click either thumbnail to open the full animation. Evidence for scroll-linked behavior a single screenshot can't show. 🟩 Safe / merged · 🟦 Advisory · 🟨 Held for review · 🟥 Blocked / closed 💰 Earn for open-source contributions like this. Gittensor lets GitHub contributors earn for the work they already do — register to start earning →. Checked by LoopOver, a quiet PR intelligence layer for OSS maintainers.
|
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
1 participant
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.
Summary
grafana-sentry-datasourceplugin, its dashboard (grafana/dashboards/sentry-issues.json),scripts/setup-sentry-datasource.sh, the docs section, and the.env.exampleblock.resource-hub.json's external Sentry bookmark link, which pointed at the pre-rename project slug (gittensory→loopover); kept the link itself since loopover-ui and the miner CLI still actively report to Sentry pending their own migration (PostHog error tracking + source maps for loopover-ui (swap the browser-sentry.ts seam) #8291, PostHog error tracking for the miner CLI (opt-in seam swap; egress-allowlist + env-reference coupling) #8292).@sentry/clihalf of this cleanup was already fully done in tonight's earlier PostHog migration PRs (fix(selfhost): read POSTHOG_CLI_PROJECT_ID/HOST from secrets, not vars #8621/fix(selfhost): unset POSTHOG_CLI_HOST when blank, don't pass empty #8622/fix(posthog): pass release-name and release-version as separate CLI flags #8624/fix(posthog): compare symbol-set release as a nested object, not a string #8629) — verified zero remaining@sentry/cliusage inrelease-selfhost.yml, only historical comments.Test plan
npx vitest runon all directly affected test files (grafana-github-datasource, grafana-resource-hub-dashboard, docs-selfhost-audit-checklist, grafana-datasource-uids, selfhost-orb-collector, selfhost-tracing, selfhost-load-file-secrets) — all passnpm run docs:drift-check— cleandocker compose -f docker-compose.yml config --quiet— validtsc --noEmit --incremental false— clean