Passive-only != disabled

[Steven Grimm]

I have a bunch of passive-only services (active checks disabled,
freshness checks enabled) that get updated by an ssh service on each host.
It works fine, but the Web UI seems to make no distinction between a
service that's defined as passive-only in the configuration and one for
which active checks have been manually disabled using the UI.  It shows
both types as "disabled," which while technically correct in terms of
active checks, is pretty misleading since the passive services are still
getting updated as intended.  Worse, it draws attention to the passive
services, e.g. on the tactical overview page, where there's a big red
"N services disabled" block that looks like it's an error indication.

Is there any way to get the UI to treat passive-only services as something
healthy and not worthy of special attention?

-Steve


-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com