Closed duylong closed 6 years ago
So, the downtime information for currently running or upcoming downtimes are available at "Upcoming downtimes":
I could add a new menu record "Acknowledgements" (or so), for a list with acknowledgement informations for host and services...
Is this what you are looking for?
That's great if we have a new menu record "Acknowledgements".
It would have been nice to list the current events on the dashboard. After I'm afraid that the dashbord becomes heavy.
Done in the elastic branch :)
Can you add the current number in the menu name ? "Acknowledgements (2)" for example
Yep. I love the idea :) To keep the load low, I set the auto refresh interval to 30 seconds for the menu.
Love it!
To avoid false positives, it would still be good to consider ACK / DOWNTIME in displaying CRIT / WARN. After I know that the implementation is not trivial.
I asked several people, and all said, that the dashboard should show critical services as critical, even if they are acknowledged or in downtime. So I will close #4.
As compromise, someone said, that the menu should only show services that are not acknowledged or in downtime. I guess this is a good solution for all of us.
Why not :) The behavior should be viewed in the documentation, for some people it will be a bug.
I added an new setting, I guess this is the best solution: Default (show all):
Hide Ack and Downtime from Dashboard and menu:
Require run of composer dump-autoload
or composer update
to work.
Finally the ACK / DOWN is hidden in the dashboard too?
Yes
A downtime on a host should not display CRIT / WARN for services in menu and dashboard. Naemon works like that for notifications.
Just schedule the downtime with Node including services
:)
This is not the default behavior in Naemon ? When a downtime is created on a host, the services also have the downtime, right? In my case, service notifications are disabled.
Nop, if you schedule a downtime for a host, only the host is in a scheduled downtime. The services of the host are still operating normally. When in comes to notifications, Naemon checks if notifications should be suppressed due to some reasons. Here is the code from Naemon's notification.c
/* if this service is currently in a scheduled downtime period, don't send the notification */
if (svc->scheduled_downtime_depth > 0) {
LOG_SERVICE_NSR(NSR_IS_SCHEDULED_DOWNTIME);
return ERROR;
}
/* if this host is currently in a scheduled downtime period, don't send the notification */
if (temp_host->scheduled_downtime_depth > 0) {
LOG_SERVICE_NSR(NSR_SERVICE_HOST_SCHEDULED_DOWNTIME);
return ERROR;
}
https://github.com/naemon/naemon-core/blob/master/src/naemon/notifications.c#L820-L830
This is the reason, why the Statusengine Ui's default option for scheduling host downtimes is Node including services
:
"Current Acknowledgements" was added.
Hi,
It will be good to list in the dashboard (or elsewhere) the current ACK/DOWNTIME informations. What do you think ?