observability: rule-25 alerts/tile/catalog for pool-reaper metrics (#44 follow-up)#52
Merged
Merged
Conversation
… follow-up) Provisioner PR #44 (sweep #8) added two hot-pool reaper metrics in provisioner/internal/pool/metrics.go. Ship their rule-25 monitoring: instant_pool_reap_total{resource_type,status,outcome} (CounterVec) - Prom rule PoolReapErrors (instant-provisioner-pool-reaper group): rate of outcome=deprovision_err|delete_err > 0 for 30m, P2 warning. - NR alert newrelic/alerts/pool-reap-errors.json. - Dashboard tile "Pool reaper — actions by status/outcome (24h)". - METRICS-CATALOG.md row. instant_pool_stuck_assigned{resource_type} (GaugeVec) - Prom rule PoolStuckAssigned (same group): max by (resource_type) > 0 for 1h, P2 operator-action warning (NOT auto-reaped — leaked shared infra needs manual anti-join). - NR alert newrelic/alerts/pool-stuck-assigned.json. - Dashboard tile "Pool items stuck 'assigned' past 30m — leaked shared infra (must be 0)". - METRICS-CATALOG.md row. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
Rule-25 monitoring follow-up for the two hot-pool reaper metrics added by provisioner PR #44 (sweep #8) in
provisioner/internal/pool/metrics.go. Each metric ships its full rule-25 set in this one PR: Prom rule + NR alert JSON + dashboard tile + METRICS-CATALOG row.instant_pool_reap_total{resource_type, status, outcome}— CounterVecReaper actions on
status="failed"pool_items;outcome∈ {reaped,deprovision_err,delete_err}.PoolReapErrors(new groupinstant-provisioner-pool-reaper):rate(...{outcome=~"deprovision_err|delete_err"}[15m]) by (resource_type,outcome) > 0 for 30m, P2 warning (reaper wedged → 'failed' pool infra accumulating).newrelic/alerts/pool-reap-errors.json(NRQLsumover the error outcomes, FACET resource_type/outcome, WARNING > 0 / 30m).instant_pool_stuck_assigned{resource_type}— GaugeVecpool_items stuck
assignedpast the 30m grace. Operator signal — deliberately NOT auto-reaped (provisioner can't distinguish a crashed-claim orphan from a live api binding; truehomie-db DROP incident class).PoolStuckAssigned(same group):max(...) by (resource_type) > 0 for 1h, P2 operator-action warning (leaked shared infra → manual resources-table anti-join).newrelic/alerts/pool-stuck-assigned.json(NRQLlatest, FACET resource_type, WARNING > 0 / 1h, LAST_VALUE fill).Notes / deviations from brief
outcome="error"for the reap alert; the actual code emitsdeprovision_erranddelete_err, so the rule/alert match those real label values.Validation
json.load.k8s/prometheus-rules.yamlparses as YAML; new group exposesPoolReapErrors+PoolStuckAssigned.🤖 Generated with Claude Code