Server stats alert still fires even when "Send XX Alerts" is disabled in server config #1011

New Issue

2026-03-22T17:05:37-05:00

GiteaMirror commented

2026-03-22 17:05:37 -05:00

Originally created by @bcat on GitHub (Feb 5, 2025).

I have the "Send Memory Alerts" option disabled for a server (since the alert triggers spuriously when using OpenZFS on Linux due to the underlying sysinfo library not knowing to filter out the ZFS ARC: #125). However, despite the setting being disabled, a critical ServerMem alert still fires when memory exceeds the "Memory Critical" threshold. This alert shows up in the status bar at the top of every Komodo page, and it appears to be impossible to dismiss or silence.

Given that I disabled the alert, I would expect it not to fire at all. But it seems disabling "Send XX Alerts" only affects the Alerter, not the Komodo UI itself. I will try setting the "Memory Warning" and "Memory" critical thresholds to 100% to force memory alerts never to trigger, however, I feel like this isn't an obvious thing to need to do. :)

Originally created by @bcat on GitHub (Feb 5, 2025). I have the "Send Memory Alerts" option disabled for a server (since the alert triggers spuriously when using OpenZFS on Linux due to the underlying sysinfo library not knowing to filter out the ZFS ARC: #125). However, despite the setting being disabled, a critical ServerMem alert still fires when memory exceeds the "Memory Critical" threshold. This alert shows up in the status bar at the top of every Komodo page, and it appears to be impossible to dismiss or silence. Given that I disabled the alert, I would expect it not to fire at all. But it seems disabling "Send XX Alerts" only affects the Alerter, not the Komodo UI itself. I will try setting the "Memory Warning" and "Memory" critical thresholds to 100% to force memory alerts never to trigger, however, I feel like this isn't an obvious thing to need to do. :)

GiteaMirror added the enhancement label 2026-03-22 17:05:37 -05:00

GiteaMirror commented

2026-03-22 17:05:38 -05:00

@bcat commented on GitHub (Feb 9, 2025):

Just to update, setting both the warning and critical thresholds to 100% seems to disable the alert for real, though I've run into some weirdness with the alert not always clearing when the threshold is changed. (Just as I went to report that, it finally cleared, though, so I've no idea what the actual problem was there.)

@bcat commented on GitHub (Feb 9, 2025): Just to update, setting both the warning and critical thresholds to 100% seems to disable the alert for real, though I've run into some weirdness with the alert not always clearing when the threshold is changed. (Just as I went to report that, it finally cleared, though, so I've no idea what the actual problem was there.)

GiteaMirror commented

2026-03-22 17:05:39 -05:00

@ffynnonbot commented on GitHub (Jun 13, 2025):

Same here.

Had to set the thresholds really high to actually get the old alert to clear even though I turned off alerting for memory.

@ffynnonbot commented on GitHub (Jun 13, 2025): Same here. Had to set the thresholds really high to actually get the old alert to clear even though I turned off alerting for memory.