Uniquely Identifiable Events in Nagios.log?

Christopher McAtackney cristoir at gmail.com
Fri Apr 3 11:26:20 CEST 2009


> Since you almost certainly want to maintain a single process to handle
> the logged lines, why not just write a tail-like program that parses
> them one by one as they're written? After all, you'd hardly want to
> slog through all the log-entries multiple times anyway.
> With this solution, I find it hard to see a need for uniqueness. should
> it happen that you still want to be able to uniquely identify lines, I
> believe a hash over the last 15 or so lines should suffice, assuming
> it's sufficiently strong (say, SHA1 or something). The chance of running
> into a collision should be very slim, and if it happens you can just
> increase the number of hashed lines.
>
> --
> Andreas Ericsson                   andreas.ericsson at op5.se

Thanks for the advice Andreas, I'll take a look into this approach.

Cheers,
Chris

------------------------------------------------------------------------------
_______________________________________________
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





More information about the Users mailing list