Skip to content
New issue

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

Document Severity Levels #252

Open
oxzi opened this issue Jul 24, 2024 · 3 comments
Open

Document Severity Levels #252

oxzi opened this issue Jul 24, 2024 · 3 comments
Labels
doc Documentation related enhancement New feature or request

Comments

@oxzi
Copy link
Member

oxzi commented Jul 24, 2024

Severity is currently only implicitly referenced, for example in the HTTP API > Process Event section.

"severity": "crit",

It would be good to document somewhere what severity levels are available.

var severityByName = map[string]Severity{
"ok": SeverityOK,
"debug": SeverityDebug,
"info": SeverityInfo,
"notice": SeverityNotice,
"warning": SeverityWarning,
"err": SeverityErr,
"crit": SeverityCrit,
"alert": SeverityAlert,
"emerg": SeverityEmerg,
}

@oxzi oxzi added enhancement New feature or request doc Documentation related labels Jul 24, 2024
@martialblog
Copy link
Member

Just curious, is there a reason that "notice" and "warning" are full words and "crit" and "emerg" aren't?

@yhabteab
Copy link
Member

yhabteab commented Jul 24, 2024

Just curious, is there a reason that "notice" and "warning" are full words and "crit" and "emerg" aren't?

Those severities are named after the journalctl/syslog(3) priority levels.

@martialblog
Copy link
Member

Maybe it should also be documented how these map to Icinga2 states... especially the Unknown state.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc Documentation related enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants