bluejay/bluejay-infra
1
0
Fork 0
Code Issues Pull Requests 14 Actions Packages Projects Releases Wiki Activity

monitoring: tag pirelay planned outage #20

Open
bluejay wants to merge 1 commits from sprint41/cx-5-pirelay-scrape-investigation into main
pull from: sprint41/cx-5-pirelay-scrape-investigation
merge into: bluejay:main
Conversation 0 Commits 1 Files Changed 1 +6
bluejay commented 2026-05-19 22:41:27 +00:00
Owner
Copy Link

Agent Report

  • Files created: []
  • Files modified: [D:\git\FlowerCore\bluejay-infra-sprint41-cx-5\apps\monitoring\noc-monitoring.yaml]
  • Tests before: 60 | Tests after: 60 | Delta: +0
  • Docs needing update: [D:\git\FlowerCore\FlowerCore.Notes\docs\infrastructure\pirelay-deployment.md updated locally with Operator action log; separate Notes commit not included in this bluejay-infra PR]
  • Decisions made (defaults): [Added metadata-only maintenance labels; did not suppress scrapes or alerts]
  • Build status: Fail (dotnet.exe test tests\bluejay-infra-lint\BluejayInfraLint.Tests.csproj = 57 passed / 3 failed; failures are pre-existing runner/ingress lint assertions unrelated to apps/monitoring/noc-monitoring.yaml)
  • PRs: [this PR]
  • Verification/blocker: Prometheus up{job=~"pimanager-app|edge-nodes",instance="pirelay"} returned both targets at 0; SSH to fcadmin@pirelay.iamworkin.lan timed out; Test-NetConnection to 10.0.58.113:5100 failed. No systemctl restart fc-pimanager.service attempted because the Pi is unreachable; physical power/access restoration remains Q-SP41-PIRELAY.
## Agent Report - **Files created:** [] - **Files modified:** [D:\git\FlowerCore\bluejay-infra-sprint41-cx-5\apps\monitoring\noc-monitoring.yaml] - **Tests before:** 60 | **Tests after:** 60 | **Delta:** +0 - **Docs needing update:** [D:\git\FlowerCore\FlowerCore.Notes\docs\infrastructure\pirelay-deployment.md updated locally with Operator action log; separate Notes commit not included in this bluejay-infra PR] - **Decisions made (defaults):** [Added metadata-only maintenance labels; did not suppress scrapes or alerts] - **Build status:** Fail (`dotnet.exe test tests\bluejay-infra-lint\BluejayInfraLint.Tests.csproj` = 57 passed / 3 failed; failures are pre-existing runner/ingress lint assertions unrelated to `apps/monitoring/noc-monitoring.yaml`) - **PRs:** [this PR] - **Verification/blocker:** Prometheus `up{job=~"pimanager-app|edge-nodes",instance="pirelay"}` returned both targets at `0`; SSH to `fcadmin@pirelay.iamworkin.lan` timed out; `Test-NetConnection` to `10.0.58.113:5100` failed. No `systemctl restart fc-pimanager.service` attempted because the Pi is unreachable; physical power/access restoration remains Q-SP41-PIRELAY.
bluejay added 1 commit 2026-05-19 22:41:28 +00:00
monitoring: tag pirelay planned outage 0a20f05525
This pull request has changes conflicting with the target branch.
  • apps/monitoring/noc-monitoring.yaml
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin sprint41/cx-5-pirelay-scrape-investigation:sprint41/cx-5-pirelay-scrape-investigation
git checkout sprint41/cx-5-pirelay-scrape-investigation
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
bluejay
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: bluejay/bluejay-infra#20
Delete Branch "sprint41/cx-5-pirelay-scrape-investigation"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?