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
Alerta error not displayed on screen when the Alerta Server down
Environment
OS: [Linux]
API version: [eg. 8.1.0]
Deployment: [Docker, Kubernetes, self-hosted]
Database: [Postgres]
Server config:
Auth enabled? Yes
Auth provider?Basic
Customer views? No
(or provide the /config endpoint output)
web UI version: [eg. 8.0.1]
To Reproduce
Steps to reproduce the behavior:
Open the Alerta and set the Refresh Interval 10 Seconds
Once the Server stopped error not seen in alerta webpage.
For web app issues, include any web browser JavaScript console errors.
Attached
Expected behavior
We use Alerta to view and handle alerts from various systems, and Alerta is a critical system for detecting errors. The Alarta user is viewing the alarmview UI, which is refreshed periodically, and alerts are coming in as expected.
We stop the Alerta web/server backend
We would expect to see some kind of error indication on the Alerta UI. But UI show no error indication. The UI simply show the same alerts, as before the server failure.
The UI is periodically trying to refresh the alert view from the backend Alerta web/server. That refresh is not possible, but UI does not present any error indication to the user.
Screenshots
Attached
The text was updated successfully, but these errors were encountered:
Issue Summary
Alerta error not displayed on screen when the Alerta Server down
Environment
OS: [Linux]
API version: [eg. 8.1.0]
Deployment: [Docker, Kubernetes, self-hosted]
Database: [Postgres]
Server config:
Auth enabled? Yes
Auth provider?Basic
Customer views? No
(or provide the
/config
endpoint output)web UI version: [eg. 8.0.1]
To Reproduce
Steps to reproduce the behavior:
For web app issues, include any web browser JavaScript console errors.
Attached
Expected behavior
Screenshots
Attached
The text was updated successfully, but these errors were encountered: