Peck Storm Active
High denied peck count detected. Review active peck sessions and check callback endpoint health.
Total Failed
—
failed peck sessions
Denied
—
—% of failed
Expired
—
—% of failed
Callback Errors
—
—% of failed
Peck Protocol State
Loading…Running sessions—
Succeeded sessions—
Failed sessions—
Success rate—
Storm threshold> 8 denied = storm active
Storm statusNo storm
Failure breakdown
Backend: GET /beak/system/status · Fields: peck_protocol.{running,succeeded,failed,failure_breakdown}
Snapshot History
0 snapshots
No snapshots yet — data appears after first load.
Storm Response Guidance
⚡ If Denied storm (>8 denied)
Check spaceduck bot callback URL validity. Review duck.peck_requested audit events. Verify beak keys are not expired. Check peck audit for requester patterns.
⏰ If Expired storm
Operators are not responding to peck requests within the TTL window. Review peck TTL configuration. Check operator notification delivery via SES. Review admin panel for stale peck sessions.
🔴 If Callback error storm
Webhook callback endpoint is failing. Verify target bot is running and reachable. Check ops runbook INC-004 for callback_error spike response steps.