Rule exceptions feature in the New Kibana Alerting Experience

**What the feature is (as Title)**

Rule exceptions feature in the New Kibana Alerting Experience

**Value proposition**
Rules eventually hit false positives, batch jobs, noisy hosts, things that look bad but are expected in your environment. The usual fix is to change the rule: raise a threshold, narrow the query, or turn it off. That often trades noise for missed incidents. Exceptions let you exclude specific cases without touching the rule itself. You can add one from an alert, reuse lists across rules, and keep the rule logic you wrote.

**Expected outcome**
You maintain a clear list of what you have chosen not to alert on, instead of weakening rules over time. Repeat false positives for the same trusted pattern stop paging on-call. Shared lists mean you do not copy the same exclusion into every rule’s ES|QL query.

The issue describes rule exceptions for the New Kibana Alerting Experience but names no files, tests, or entry points. Start by locating the alerting and rule-exception areas in Kibana, then define the scope and acceptance criteria for adding, reusing, and applying exception lists.

Written by the indexing model from the issue text.