Skip to content

docs(observability): record the silence actually in force on shiva - #201

Merged
Gerrrt merged 1 commit into
mainfrom
gerrrt/ilo-battery-condition-shiva-bd4c9d
Aug 31, 2026
Merged

Gerrrt merged 1 commit into
mainfrom
gerrrt/ilo-battery-condition-shiva-bd4c9d

Conversation

@Gerrrt

@Gerrrt Gerrrt commented Aug 31, 2026

Copy link
Copy Markdown
Owner

Follow-up to #200, which merged at 13:53:59Z while the verification below was
still running.

Why this is needed

#200 recorded silence 3ffc313f-7154-459c-9f62-7c9a432bc97e in three places.
That silence was deleted at 13:43:50Z — ten minutes before #200 merged — so
both alerts could be watched notifying for real. main therefore currently
points at an expired silence in the rule header, the roadmap entry and the
runbook.
This replaces it with the one now in force,
bfdfff66-d9c3-4df4-9495-f1f38ebf93c1: same matchers, same 2026-10-01
expiry, so the accept-with-expiry decision is unchanged and only the identifier
moves.

What the deletion bought

Both alerts were watched from pending into firing against live hardware, and
both reached the default receiver with zero webhook failures:

fired value evidence
IloBatteryCondition 14:07Z 13 cpqHeSysBatterySparePartNum=815983-001 on the alert, receivers=['default'], silencedBy=[]
IloWriteCacheDisabled 14:37Z 5 receivers=['default'], silencedBy=[]

IloHardwareDegraded stayed inactive throughout with cpqDaCntlrCondition
reading 3 — the > 3 threshold doing its job against real hardware rather
than a fixture, which is the one thing the unit tests could not prove.

All three rules held health=ok, so the group_left join matches at evaluation
time and does not error.

Incidentally AlertmanagerNotificationsFailing cleared to inactive on its own
during this — it had been firing off pre-restart failures aging out of its
window, and nothing has failed since.

The silence is back on and both alerts now read state=suppressed,
silencedBy=['bfdfff66-d9c3-4df4-9495-f1f38ebf93c1'].

Verification

./scripts/validate.sh passes end to end. No reference to the expired
3ffc313f… survives anywhere in the tree.

🤖 Generated with Claude Code

The first silence was deleted so both alerts could be watched notifying for
real, which means the UUID written into the rule header, the roadmap entry and
the runbook pointed at an expired silence. Replace it with the one now in
force, bfdfff66-d9c3-4df4-9495-f1f38ebf93c1 — same matchers, same 2026-10-01
expiry, so the decision is unchanged and only the identifier moves.

Record what the deletion bought while it was off. Both alerts were watched
through pending into firing and both reached the default receiver with zero
webhook failures: IloBatteryCondition at 14:07Z carrying
cpqHeSysBatterySparePartNum=815983-001 and $value 13, IloWriteCacheDisabled at
14:37Z at 5. IloHardwareDegraded stayed inactive throughout with
cpqDaCntlrCondition reading 3, which is the > 3 threshold doing its job against
live hardware rather than a fixture. What is suppressed is now known-working
rather than assumed-working, and that is the part worth having in the record —
a silence over an unproven rule is the failure mode this repository keeps
re-learning.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@Gerrrt
Gerrrt merged commit d61f29d into main Aug 31, 2026
3 checks passed
@Gerrrt
Gerrrt deleted the gerrrt/ilo-battery-condition-shiva-bd4c9d branch August 31, 2026 14:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant