Hi Matt -
The suggested additions would help in finding historical data, but
they are not very practical when you:
1. are using short log rotation times (i.e. hourly)
2. monitor a large number (several thousand) hosts/services
You'd just end up with very cluttered log files. I'm not really sure
what the best way to handle this stuff is...
On 17 Feb 2003 at 13:33, Matt Clay wrote:
> I ran into the host availability reporting problem discussed on the
> Nagios Users mailing list in the thread "Host Availability Report".
>
> As I understand it, the given solutions were:
> 1) Increase the backtrack period.
> 2) Set the default host state manually.
>
> I used #1 to solve my problem temporarily. However, I think there are
> better ways to fix this...
>
> 1) Have Nagios record all host states in the log file during log
> rotation. This would remove the need for backtracking entirely, as all
> host states would be present at the start of each log file.
>
> 2) Have Nagios record all host states on a specified interval. Simply
> ensure that the interval is less than or equal to the backtrack period.
> That way, whenever you backtrack, you are guaranteed to find your
> initial host states. In the case of daily log rotation, this interval
> would need to be 4 days or less.
>
> Unless I've missed something, I think that one of these solutions is
> needed to ensure that Nagios can always find initial state for hosts.
> Otherwise, given that hosts are up for long enough, Nagios won't be able
> to find initial state in any reasonable backtracking period.
>
> --
>
> Matt Clay
> Systems Administrator
> Western States Electric
> 503-653-8619 (phone)
> 503-653-2279 (fax)
>
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Nagios-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/lis ... gios-devel
>
Ethan Galstad,
Nagios Developer
---
Email: [email protected]
Website: http://www.nagios.org
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]