Re: [Nagios-devel] Really slow log2ndo
Posted: Wed Sep 24, 2008 8:10 am
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
[ Resending as this message bounced after 5 days
]
On 19/09/08 07:17 AM, Thomas Guyot-Sionnest wrote:
>
> Any reason why not using a single table with all the common log entry
> stuff? Would likely be only auto-increment + date stamp, of better yet
> (with some nagios modification) a TAI timestamp as the resolution would
> be high enough to use it as a primary key, and possibly (if we want to
> allow aggregating multiple Nagios monitoring servers together) a
> monitoring host id as well.
>
> Then each notification type would reference to this table, so that that
Oops.. I meant each log type.
Also it wasn't explicitly mentioned but each log type would be in a
separate table with a reference top the single one.
> you could use them standalone (possibly joined to the single one if you
> have a monitoring host id), but also join them all with the single table
> to get a full log representation.
>
> I forgot how this is named, but IMHO that would be the best
> representation for a nagios log.
- --
Thomas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFI2gPn6dZ+Kt5BchYRAqoUAJ9cIV6Fbt8tnxrzh26wbgg/hHIFewCfck65
a7runJi0Jn6uJYc1zinQ+SE=
=yi5C
-----END PGP SIGNATURE-----
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]
Hash: SHA1
[ Resending as this message bounced after 5 days
]On 19/09/08 07:17 AM, Thomas Guyot-Sionnest wrote:
>
> Any reason why not using a single table with all the common log entry
> stuff? Would likely be only auto-increment + date stamp, of better yet
> (with some nagios modification) a TAI timestamp as the resolution would
> be high enough to use it as a primary key, and possibly (if we want to
> allow aggregating multiple Nagios monitoring servers together) a
> monitoring host id as well.
>
> Then each notification type would reference to this table, so that that
Oops.. I meant each log type.
Also it wasn't explicitly mentioned but each log type would be in a
separate table with a reference top the single one.
> you could use them standalone (possibly joined to the single one if you
> have a monitoring host id), but also join them all with the single table
> to get a full log representation.
>
> I forgot how this is named, but IMHO that would be the best
> representation for a nagios log.
- --
Thomas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFI2gPn6dZ+Kt5BchYRAqoUAJ9cIV6Fbt8tnxrzh26wbgg/hHIFewCfck65
a7runJi0Jn6uJYc1zinQ+SE=
=yi5C
-----END PGP SIGNATURE-----
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]