Yes, I'm always frustrated when I set up "per document monitors" in OpenSearch Alerting and find that I cannot apply action throttling. This limitation results in an overwhelming number of alerts for the same issue, leading to alert fatigue and making it challenging to focus on the most critical issues.
What solution would you like?
I would like the OpenSearch Alerting functionality to support action throttling for "per document monitors" just as it does for other types of monitors. Action throttling should allow users to define a cooldown period during which repeated actions for the same conditions are suppressed, thereby reducing noise and enhancing the focus on new or unaddressed issues.
What alternatives have you considered?
As an alternative, I have considered using other monitor types that support action throttling, but these do not meet my specific use case requirements as effectively as a "per document monitor" would. I have also looked into external tools and scripts to manually throttle alerts, but this approach is cumbersome and introduces unnecessary complexity into our monitoring setup.
Do you have any additional context?
Adding action throttling to "per document monitors" would bring consistency across the monitoring functionality in OpenSearch, improve operational efficiency by reducing unnecessary alert noise, and give users more control over their alerting strategies. This feature would significantly enhance the usability and effectiveness of OpenSearch Alerting for scenarios requiring detailed, document-level monitoring.
praveensameneni
commented
3 months ago
Is your feature request related to a problem?
Yes, I'm always frustrated when I set up "per document monitors" in OpenSearch Alerting and find that I cannot apply action throttling. This limitation results in an overwhelming number of alerts for the same issue, leading to alert fatigue and making it challenging to focus on the most critical issues.
What solution would you like?
I would like the OpenSearch Alerting functionality to support action throttling for "per document monitors" just as it does for other types of monitors. Action throttling should allow users to define a cooldown period during which repeated actions for the same conditions are suppressed, thereby reducing noise and enhancing the focus on new or unaddressed issues.
What alternatives have you considered?
As an alternative, I have considered using other monitor types that support action throttling, but these do not meet my specific use case requirements as effectively as a "per document monitor" would. I have also looked into external tools and scripts to manually throttle alerts, but this approach is cumbersome and introduces unnecessary complexity into our monitoring setup.
Do you have any additional context?
Adding action throttling to "per document monitors" would bring consistency across the monitoring functionality in OpenSearch, improve operational efficiency by reducing unnecessary alert noise, and give users more control over their alerting strategies. This feature would significantly enhance the usability and effectiveness of OpenSearch Alerting for scenarios requiring detailed, document-level monitoring.