alert_not_silenced

Summary

{0}

Help

nanook ctl state shows current silences; only active silences can be removed

Details

When this fires

POST /unsilence (or the equivalent websocket RPC) hit the dispatch layer in nanook-admin/src/dispatch.rs and the engine reported no live silence matching the supplied expression. Maybe the silence has already expired, maybe an operator just removed it, or the expression has a stray space compared to what's stored.

What to check

• nanook ctl state lists active silences with their exact expr strings; re-issue the unsilence with that string copied verbatim:

nanook ctl unsilence "cpu.usage > 90"

• If you expected it to still be active, check whether duration_secs lapsed or another operator hit /unsilence first.