-
Notifications
You must be signed in to change notification settings - Fork 20
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
Livestatus incorrectly reporting that contact is not in host notification period #74
Comments
Actually, checking on this again, it looks like service_notification_period and host_notification_period return blanks now. Not sure what changed, I haven't updated anything, all contacts are still using all the different timeperiods they were before, and they're working; the contacts are receiving notifications during their timeperiods... This is interesting because notification_period returns the proper value when querying Hosts. The contact object sets those as follows:
The host object sets it like this:
I'm not sure how important that ALSO, this section is commented out of the contact object, but it is NOT commented out of the host object:
|
Oh ho ho! Uncommenting the:
fixed it! Now livestatus is showing me the contacts' notification period names, AND showing that they are in (or out of) the periods as expected! |
I have a contact set to use the 24x7 timeperiod for host notifications. I've tested notifications, and they do receive notifications as expected.
In Livestatus, if I run the following query:
No contacts appear. If I remove the filter, all my contacts appear. Livestatus is correctly reporting that the contact is using the 24x7 timeperiod, but it says that they're not in their host notification period:
Using newest Livestatus module from git.
The text was updated successfully, but these errors were encountered: