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
{{ message }}
This repository has been archived by the owner on Oct 18, 2024. It is now read-only.
Unwittingly, I designed Alertinator to use a subset of syslog's severity levels (defined in rfc5424). It seems reasonable to support the full set.
It does seem like perhaps a bit much, though - not only will users need to determine which alert level is appropriate, but it makes user config more complex, particularly since we don't have a good way of specifying "this level and up".
The text was updated successfully, but these errors were encountered:
particularly since we don't have a good way of specifying "this level and up".
We do -- that's the beauty of the bitmask. With the 3 levels you have today, reporting all except Critical would be ALL & ~CRITICAL. "Warning and up" could be ALL & ~NOTICE or WARNING | CRITICAL.
👍 to this idea.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Unwittingly, I designed Alertinator to use a subset of syslog's severity levels (defined in rfc5424). It seems reasonable to support the full set.
It does seem like perhaps a bit much, though - not only will users need to determine which alert level is appropriate, but it makes user config more complex, particularly since we don't have a good way of specifying "this level and up".
The text was updated successfully, but these errors were encountered: