[Response Ops] Refactor error handling in alerting task runner #134579
Labels
Feature:Alerting/RulesFramework
Issues related to the Alerting Rules Framework
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
We added stack traces for errors thrown in the alerting task runner in this PR. In the task runner, errors are caught and rethrown possibly multiple times so sometimes the original stack trace is lost. To get around that, we're logging errors from the rule executors in multiple places in order to capture the original stack trace. It would be nice to refactor this error logic so we can log in a single place while preserving the original stack trace.
Adding to meta issue
The text was updated successfully, but these errors were encountered: