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
Issue Summary
When I have a detail view for an alert in state "Critical" open in the WebUI, events setting that alert to "OK" are processed, but the state does not change. Event etc. are set, but the state remains
Environment
OS: Debian 12.7
API version: alertad 9.0.4
Deployment: self-hosted
For self-hosted, WSGI environment: apache/gunicorn
Database: Postgres
Server config:
Auth enabled? Yes
Auth provider? LDAP
Customer views? No
web UI version: 8.7.0
CLI version: 8.5.3
To Reproduce
Steps to reproduce the behavior:
Send a critical alert to Alerta
Open the "Detail" view in the WebUI
Send an OK alert to Alerta for the same resource, event etc. so that it is correlated
The state of the alert does not change to OK, but the remainder of the values of the "OK" alert are recorded properly.
If this should not be sufficient I'll need to set up a separate test environment for reproducing it reliably, as currently I only have the customer's production environment available.
Expected behavior
Same as above, but with the alert being updated to "OK" and closed.
The text was updated successfully, but these errors were encountered:
Issue Summary
When I have a detail view for an alert in state "Critical" open in the WebUI, events setting that alert to "OK" are processed, but the state does not change. Event etc. are set, but the state remains
Environment
OS: Debian 12.7
API version: alertad 9.0.4
Deployment: self-hosted
For self-hosted, WSGI environment: apache/gunicorn
Database: Postgres
Server config:
Auth enabled? Yes
Auth provider? LDAP
Customer views? No
web UI version: 8.7.0
CLI version: 8.5.3
To Reproduce
Steps to reproduce the behavior:
If this should not be sufficient I'll need to set up a separate test environment for reproducing it reliably, as currently I only have the customer's production environment available.
Expected behavior
Same as above, but with the alert being updated to "OK" and closed.
The text was updated successfully, but these errors were encountered: