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

[codex] monitoring: mirror Sprint 57 coverage rules #34

Open
bluejay wants to merge 1 commits from codex/s57-monitoring-coverage into main
pull from: codex/s57-monitoring-coverage
merge into: bluejay:main
Conversation 0 Commits 1 Files Changed 2 +177 -5
bluejay commented 2026-06-04 03:48:09 +00:00
Owner
Copy Link

Summary

  • mirrors the Sprint 57 Cx-5 monitoring source into apps/monitoring/noc-monitoring.yaml
  • carries the seven added Traefik probe targets into the GitOps migration mirror
  • mirrors the Epson stale-series alert and Grafana IRC delivery rule
  • mirrors the live github-runner exclusion across KubeContainerRestartingFrequently, KubeContainerCrashLooping, and KubeDeploymentReplicasMismatch while preserving dedicated runner alerts
  • adds five self-contained bluejay-infra lint tests for monitoring coverage parity

Validation

  • focused monitoring lint: 5 passed, 0 failed
  • focused monitoring lint with FLOWERCORE_NOTES_ROOT override: 5 passed, 0 failed
  • full bluejay-infra lint: 87 passed, 4 failed from existing fleet-manifest baseline issues
  • lane diff check passed for apps/monitoring/noc-monitoring.yaml and tests/bluejay-infra-lint/MonitoringCoverageLintTests.cs

Merge status

Held until the existing full-lint baseline failures are resolved or explicitly accepted: updatecenter public Method(POST), fc-device-management ArgoCD manifest/discovery, and github-runner-sharedpos replica count.

## Summary - mirrors the Sprint 57 Cx-5 monitoring source into apps/monitoring/noc-monitoring.yaml - carries the seven added Traefik probe targets into the GitOps migration mirror - mirrors the Epson stale-series alert and Grafana IRC delivery rule - mirrors the live github-runner exclusion across KubeContainerRestartingFrequently, KubeContainerCrashLooping, and KubeDeploymentReplicasMismatch while preserving dedicated runner alerts - adds five self-contained bluejay-infra lint tests for monitoring coverage parity ## Validation - focused monitoring lint: 5 passed, 0 failed - focused monitoring lint with FLOWERCORE_NOTES_ROOT override: 5 passed, 0 failed - full bluejay-infra lint: 87 passed, 4 failed from existing fleet-manifest baseline issues - lane diff check passed for apps/monitoring/noc-monitoring.yaml and tests/bluejay-infra-lint/MonitoringCoverageLintTests.cs ## Merge status Held until the existing full-lint baseline failures are resolved or explicitly accepted: updatecenter public Method(POST), fc-device-management ArgoCD manifest/discovery, and github-runner-sharedpos replica count.
bluejay added 1 commit 2026-06-04 03:48:10 +00:00
monitoring: mirror Sprint 57 coverage rules 0ed9b989fa
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 codex/s57-monitoring-coverage:codex/s57-monitoring-coverage
git checkout codex/s57-monitoring-coverage
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#34
Delete Branch "codex/s57-monitoring-coverage"

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?