RFC: NDO nagios_objects table issue with is_active flag

[Lars Michelsen]

Hi Ethan, Hi List,
we've spotted some problem with the NDO table nagios_object regarding
the is_active flag and its values.

When selecting current objects in NagVis we use the is_active flag.
The default value of this flag is 0. That default value makes sense
when some deprecated and current objects are stored in the table. The
current objects are set to is_active=1.

The current objects are only set to active when BROKER_RETENTION_DATA
is activated or "event_broker_options" is set to 0.

When the admin disables BROKER_RETENTION_DATA all objects have
is_active=0. Cause there are no deprecated object all objects should
be set to is_active=1.

Some users in the German Nagios Portal reported that Nagios starts up
more faster when they turn of BROKER_RETENTION_DATA (up to 30 seconds
quicker). It would be nice to change the default value of is_active to
1 when BROKER_RETENTION_DATA is turned off.

At the moment we added a small woraround to NagVis which checks
whether there is one object with is_active=1. If there is one it
considers the is_active flag. If no data record with is_active=1 is
found NagVis ignores this flag.

It could also be possible to think of setting default value of
is_active to 1 in all cases and only set deprecated objects to 0.
Maybe this would boost the restart time when BROKER_RETENTION_DATA is
enabled.

Lars

-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php