Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This change introduces configurable alert time windows for server CPU, memory, and disk alerts to reduce noise from short-lived spikes. Instead of triggering alerts immediately when thresholds are crossed, alerts can now be configured to open only if the condition persists for a specified number of seconds. A value of 0 preserves the existing behavior and triggers alerts immediately (after two consecutive checks).
Inspiration for this feature comes from how beszel handles notification thresholds.
This screenshot shows how users can configure the feature. Keeping the value at the default of
0disables the time window and keeps the existing behavior.