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
All alerts coming from nrpe-exporter have an hardcoded severity set to critical.
In order to support PagerDuty dynamic-notifications would be beneficial if the status of the check is reflected into the severity label of the alert.
An nrpe check can have one of the following status code that needs to be translate to a severity label as following
0 = OK -> this doesn't produce any alert
1 = Warning -> severity=warning
2 = Critical -> severity=critical
3 = Unknown -> severity=error
The text was updated successfully, but these errors were encountered:
This has been resolved by #101
Sorry, something went wrong.
No branches or pull requests
Enhancement Proposal
All alerts coming from nrpe-exporter have an hardcoded severity set to critical.
In order to support PagerDuty dynamic-notifications would be beneficial if the status of the check is reflected into the severity label of the alert.
An nrpe check can have one of the following status code that needs to be translate to a severity label as following
0 = OK -> this doesn't produce any alert
1 = Warning -> severity=warning
2 = Critical -> severity=critical
3 = Unknown -> severity=error
The text was updated successfully, but these errors were encountered: