Repository navigation
Replies: 5 comments 1 reply
|
Hi @DRO34, thanks for the suggestion! You are right, currently alerts are fire-and-forget: they trigger when a threshold is crossed but there is no "resolved" notification when the metric drops back to normal. This is a great idea. We are adding it to the roadmap. The plan would be to track alert state so that when a condition clears, a recovery notification is sent (email, webhook, etc.) with the resolved status. I have created a feature request issue to track this: will link it here shortly. |
|
Hi Michael, thanks for flagging this! You're right, that severity badge was showing a hardcoded French label ("CRITIQUE") instead of following your interface language. It now goes through the translation system, so it will correctly read CRITICAL (or the equivalent in your selected language). While we were at it, we also cleaned up a few other spots where a stray French label could surface in the UI. This will ship in the next release. |
|
@DRO34 The remaining hardcoded French strings in the alerting UI have moved to translation keys, so that part of the interface is now consistent in every language. Released in v1.4.6 — the release notes list every image to pull: Could you confirm it behaves as expected on your side? |

Uh oh!
There was an error while loading. Please reload this page.
Hello, simple one here.
I notice when we get alerts, for example, high memory usage.. We do not get any kind of resolved alerts to know the alert is no longer an issue.. Is this something that can be implemented?
All reactions