aiai-bot commented on issue #3952: URL: https://github.com/apache/hertzbeat/issues/3952#issuecomment-3743486407
<!-- code-pr-reviewer --> Based on the code analysis, the system does send recovery (resolved) notifications through the same flow as firing alerts: - `hertzbeat-alerter/src/main/java/org/apache/hertzbeat/alert/calculate/realtime/MetricsRealTimeAlertCalculator.java:362-372` confirms resolved alerts are sent - NoticeRule matching logic at `hertzbeat-alerter/src/main/java/org/apache/hertzbeat/alert/service/impl/NoticeConfigServiceImpl.java:206-252` doesn't distinguish alert states - Default `filterAll=true` at `hertzbeat-common/src/main/java/org/apache/hertzbeat/common/entity/alerter/NoticeRule.java:111` should forward all alerts **The most likely cause is configuration** - recovery notifications may be filtered out if: 1. **NoticeRule has label filtering** configured that doesn't match the resolved alert labels (dynamic labels may differ between firing/resolved states) 2. **Time period constraints** - recovery occurred outside the configured notification window 3. **NoticeRule is disabled or wasn't saved correctly** Could you please share: - Your NoticeRule configuration (especially label filters and time constraints) - Alerter module logs showing whether the resolved alert entered the notification pipeline This will help identify the exact filtering condition preventing recovery notifications. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
