We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Severity is currently only implicitly referenced, for example in the HTTP API > Process Event section.
icinga-notifications/doc/20-HTTP-API.md
Line 36 in f21e6e1
It would be good to document somewhere what severity levels are available.
icinga-notifications/internal/event/severity.go
Lines 24 to 34 in 61277c4
The text was updated successfully, but these errors were encountered:
Just curious, is there a reason that "notice" and "warning" are full words and "crit" and "emerg" aren't?
Sorry, something went wrong.
Those severities are named after the journalctl/syslog(3) priority levels.
journalctl/syslog(3)
Maybe it should also be documented how these map to Icinga2 states... especially the Unknown state.
No branches or pull requests
Severity is currently only implicitly referenced, for example in the HTTP API > Process Event section.
icinga-notifications/doc/20-HTTP-API.md
Line 36 in f21e6e1
It would be good to document somewhere what severity levels are available.
icinga-notifications/internal/event/severity.go
Lines 24 to 34 in 61277c4
The text was updated successfully, but these errors were encountered: