Skip to content

feat(alerts): signal-type-aware cooldown (Issue vs MonitorMissed) #366

Open

Description

@ajianaz

Summary

Alert cooldown is per-rule across signal types: an Issue alert and a MonitorMissed alert sharing one rule window can suppress each other. Found in #364 security review (parity with old logic, not a regression).

Why

A missed-monitor alert being silenced by an unrelated recent issue alert (or reverse) is surprising. Signal-type-aware cooldown windows give correct urgency for each type.

Acceptance criteria

  • Cooldown keyed by (rule, signal-type) — Issue and MonitorMissed tracked independently
  • Tests prove cross-type suppression no longer occurs

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions