Why is the UX for passive checks disfavoured?

Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
Locked
hablutzel1
Posts: 1
Joined: Sun Feb 16, 2020 7:02 pm

Why is the UX for passive checks disfavoured?

Post by hablutzel1 »

I have only one service with Active Checks disabled (active_checks_enabled is 0), but Passive Checks enabled (passive_checks_enabled is 1) and the Freshness Threshold set (freshness_threshold is 600).

Now, when I go to Tactical Overview I see the following:
tactical_overview_treatment_of_passive_only_checks.png
Where the UI kind of suggests (at least to a non-Nagios expert user) that there are problems.

Additionally, in the Services view:
question_mark_for_passive_service_check.png
The question mark ("?") symbol suggest that something for that service is unknown.

So, why are the passive-only checks receiving such a disfavoured UX treatment, even when the Freshness Threshold is set, which (if I'm not wrong) guarantees that check results are expected with a given frequency, otherwise the check would alert. Wouldn't it be better to provide a more friendly UX treatment for passive-only checks?, at least when the Freshness Threshold is set?

PS: Running Nagios Core 4.4.6.
Locked