You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
There is no indication from the UI that a test notification has failed to send to the destination.
It is not possible to test a destination w/o trying to configure an alert.
Describe the solution you'd like
A pop-up alert for failures to test the alert.
Ability to test destinations separately from alerts
The text was updated successfully, but these errors were encountered:
By design we don't throw an exception whenever we are not able to send an alert. We mark that alert in the error state and send that error as a part of the response of the monitor execution result. Since the monitor execution succeeds the response doesn't throw any error and in the frontend code we check for the response status of the request and not the status of the action (which is present in the response content). This results in the front end not showing an error for the action which was not executed.
This implementation is correct from the backend as the monitor execution succeeded and the action is marked in the error state. The problem lies in the front-end response parsing where we should check explicitly for the action response.
Wednesday May 19, 2021 at 17:16 GMT
Originally opened as opendistro-for-elasticsearch/alerting#378
Is your feature request related to a problem? Please describe.
There is no indication from the UI that a test notification has failed to send to the destination.
It is not possible to test a destination w/o trying to configure an alert.
Describe the solution you'd like
A pop-up alert for failures to test the alert.
Ability to test destinations separately from alerts
The text was updated successfully, but these errors were encountered: