(no subject)

[Marc Powell]

> -----Original Message-----
> From: nagios-users-bounces at lists.sourceforge.net [mailto:nagios-users-
> bounces at lists.sourceforge.net] On Behalf Of Prigge Scott
> Sent: Wednesday, April 04, 2007 11:34 AM
> To: nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] (no subject)
> 
> I recently upgraded from 1.0b to 2.7. I noticed that immediately after
> my daily log rotation, the current state of all hosts and services is
> entered in the log file. As I have thousands of hosts/services, this
> makes the log (in my case) unnecessarily large, and was hoping to find
> an option to prevent those states from being logged.

This was a new feature introduced in 2.0 to reduce the amount of time
that a host or service status would be UNDETERMINED for reporting.
Previously, nagios couldn't determine the state of a host or service in
a log file unless that host or service changed state. This required
users to manually set the first assumed state for accurate reporting.
This fix makes that unnecessary. AFAIK, there's no way to disable it
outside of code editing.

http://nagios.sourceforge.net/docs/2_0/whatsnew.html

"Logging changes - Initial host and service states are now logged a bit
differently. Also, the initial states of all hosts and services are
logged immediately after all log rotations. This should help with all
those "undetermined time" problems in the availability and trends CGIs."

--
Marc

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null