Kibana rules vs connectors: where should alert throttling live to cut noise without delaying critical notifications
We run Kibana alerting (8.x) with rules feeding several connectors (email, Slack, and a webhook into our incident tool). The goal is a single, predictable throttling strategy so channels stay actionable: no floods during flapping conditions, but also no silent delay when a genuinely important alert fires. Kibana offers noise controls on the rule side—action
kibana