KrakenJS Alerts: Silence Duration Cannot Be Environment‑Specific

KrakenJS Alerts: Silence Duration Cannot Be Environment‑Specific

The alerts package allows a silence setting that suppresses messages matching a regular expression for a fixed duration (default 10 minutes). The duration is hard‑coded in the library and cannot be overridden per deployment environment. Consequently, a single configuration file must be used across all stages, or developers must duplicate the file with hard‑coded values, which defeats the purpose of a shared alerting strategy.

While the threshold field can filter by severity, there is no mechanism to tie the silence window to the alert source or to scale it dynamically with the frequency of events. In high‑traffic environments, this leads to repeated bursts of notifications once the silence period expires.

Given the lack of per‑environment silence configuration and the absence of automatic deduplication, teams must implement custom logic to avoid notification noise.

Questions:

• Is there an upcoming release that will expose a per‑environment silence duration configuration?
• Can silence rules be combined with dynamic thresholds to adapt suppression based on alert frequency?
• What concurrency safeguards are recommended when multiple processes generate alerts that might bypass the simple timestamp comparison?