Bug report or feature request: Make "Next update" information N/A when active checks disabled

[Napsty]

So yes, this could either be a bug or a feature request. Depending who reads this and how this is understood.

The current way Icingaweb2 handles a service object is to show its last and its next (scheduled) check time.

In the screenshot above, the "Last update" information shows when the check ran the last time. The "Next update" information shows when the check is (supposed) to run at the next schedule.

However the "Next update" information only makes sense when this particular check is an active check.

I have this current service check (doesn't matter if it uses nrpe or anything else), setting active checks to false:

object Service "Test Service" {
  import "generic-service"
  enable_active_checks = false
  enable_notifications = false
  volatile = true
  host_name = "testhost"
  check_command = "nrpe"
  vars.nrpe_command = "check_test"
}

Icinga 2 correctly handles it; meaning the check is not executed automatically. Only when launching the check in the UI (using "Check now"), the check is (manually) run and the "Last update" information changes.

Describe the solution you'd like

It would be nice, if Icingaweb2 would detect that this service isn't an "active check". It actually already does so by showing the toggles:

But in this situation, set the "Next update" information to a static "N/A" or to another informational output, e.g. "Active check not enabled" or similar.

[zampat]

I appreciate this suggestion to make evidence that "passive checks" should not be influenced by a user.

A good solution would be to provide a permission setting in roles management to disable the action "re-schedule check". This would affect all uses, but could help to prevent them for impacting the monitoring.