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

check_period is listed as required even though it's not #59

Open
catharsis opened this issue May 6, 2016 · 1 comment
Open

check_period is listed as required even though it's not #59

catharsis opened this issue May 6, 2016 · 1 comment

Comments

@catharsis
Copy link
Contributor

http://www.naemon.org/documentation/usersguide/objectdefinitions.html#host_definition lists check_period as a required attribute. This is not the case; if left unset the check_period for a host will be 24x7.

@Herkum
Copy link
Contributor

Herkum commented Dec 21, 2018

Referring to the Nagios documentation, it states that it checks it on a as needed basis, which appears to be a 24x7 time frame.

When checking the configuration, it does work, but it returns all the check_period fields as warnings, so it will run, so the question is really what does as needed basis mean? Does it do checks outside of notification windows? Does it do it only when it sees it scheduled to a refresh setting? You not needing a check_period is very ambiguos and everything else about Naemon is strictly defining the behavior of the application.

To be honest, in my opinion, I think it should be changed from a "Warning" to an "Error" and ensure that it is a required field. The only reason I could not too is that it would break backwards compatibility.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants