fix(rebrand): full-cutover rename Prometheus/Alertmanager/Grafana observability identifiers - #5768
Merged
Merged
Conversation
…ervability identifiers
Renames the last unrenamed identifier surface in the observability
stack: the app's own Prometheus scrape job (job_name: gittensory ->
loopover, gittensory-backup -> loopover-backup, matching the already-
renamed loopover:8787 compose service), the up{job="gittensory"} == 0
expr the LoopoverTargetDown alert reads it through, and the three
AMS-miner alert rule GROUP names (gittensory-miner-prediction/
-portfolio-queue/-governor -> loopover-miner-*) -- confirmed no
Alertmanager routing depends on these group names.
Also fixes directly-adjacent stale prose discovered while verifying:
runbook/summary text quoting the already-renamed loopover-miner CLI,
alertmanager.yml's header comment + docs URL (updated to the canonical
loopover.ai domain), and Grafana dashboard description strings in
ai-usage.json/miner-usage.json/resource-hub.json/ams-ledgers.yml.
Deliberately not touched: the real JSONbored/gittensory GitHub repo
and Sentry-project references embedded in these same dashboard files.
Contributor
|
Superagent didn't find any vulnerabilities or security issues in this PR. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #5768 +/- ##
=======================================
Coverage 95.07% 95.07%
=======================================
Files 582 582
Lines 46212 46212
Branches 14819 14819
=======================================
Hits 43936 43936
Misses 1516 1516
Partials 760 760
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
This was referenced Jul 14, 2026
Closed
Closed
Closed
Closed
Closed
Closed
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.
Summary
job_name: gittensory→loopover,gittensory-backup→loopover-backup, matching the already-renamedloopover:8787compose service) and theup{job="gittensory"} == 0expr theLoopoverTargetDownalert reads it through.gittensory-miner-prediction/-portfolio-queue/-governor→loopover-miner-*) — confirmed no Alertmanager routing config depends on these group names before renaming.loopover-minerCLI,alertmanager.yml's header comment + docs URL (updated to the canonicalloopover.aidomain), and Grafana dashboard description strings inai-usage.json/miner-usage.json/resource-hub.json/ams-ledgers.yml.Deliberately not touched: the real
JSONbored/gittensoryGitHub repo and Sentry-project references embedded in these same dashboard files.Test plan
npm run typecheckcleannpx vitest run— 838 files / 16257 tests passed (2 pre-existing skips)npm run selfhost:validate-observabilitycleannpm run test:cigate green end-to-end