[Nagios-devel] NSCA bottleneck / NSCA Timestamp
Posted: Mon Nov 19, 2007 9:27 am
Hi list,
as many time before again I suffered from the NSCA bottle neck in
Nagios. It's not new that NSCA can cause huge latency. Ton already
mentioned this in his blog
(http://altinity.blogs.com/dotorg/2006/1 ... ca_da.html).
At my last project my workaround for this problem was to use the
service_perfdat_file for caching and every 10 seconds the
service_perfdata_file_processing_command to transfer this cached data to
the master via one nsca call. This approach reduces/solves the latency
problem. @Ton: with this approach there should be no need of any caching
script and should work for hosts and services, or am I missing
anything?=20
Since nsca doesn't transfer any timestamps the reporting will not be
correct at the master site! Ok, these 10 seconds delay isn't a big issue
but I wonder why doesn't nsca transport the original timestamp?=20
Because I would like the reporting to be as accurate as possible I would
like to patch nsca. If changing nsca to include the timestamp would be
worthwhile and there is any change for this patch to become part of nsca
I write this patch.=20
So anybody interested in this patch or any comments to this problem?
Cheers,
Gerd =20
--=20
Gerd Mueller =20
Senior Consultant
NETWAYS GmbH | Deutschherrnstr. 47a | D-90429 N=FCrnberg=20
Tel: +49 911 92885-0 | Fax: +49 911 92885-33=20
GF: Julian Hein | AG N=FCrnberg HRB18461=20
=20
http://www.netways.de | [email protected]=20
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]
as many time before again I suffered from the NSCA bottle neck in
Nagios. It's not new that NSCA can cause huge latency. Ton already
mentioned this in his blog
(http://altinity.blogs.com/dotorg/2006/1 ... ca_da.html).
At my last project my workaround for this problem was to use the
service_perfdat_file for caching and every 10 seconds the
service_perfdata_file_processing_command to transfer this cached data to
the master via one nsca call. This approach reduces/solves the latency
problem. @Ton: with this approach there should be no need of any caching
script and should work for hosts and services, or am I missing
anything?=20
Since nsca doesn't transfer any timestamps the reporting will not be
correct at the master site! Ok, these 10 seconds delay isn't a big issue
but I wonder why doesn't nsca transport the original timestamp?=20
Because I would like the reporting to be as accurate as possible I would
like to patch nsca. If changing nsca to include the timestamp would be
worthwhile and there is any change for this patch to become part of nsca
I write this patch.=20
So anybody interested in this patch or any comments to this problem?
Cheers,
Gerd =20
--=20
Gerd Mueller =20
Senior Consultant
NETWAYS GmbH | Deutschherrnstr. 47a | D-90429 N=FCrnberg=20
Tel: +49 911 92885-0 | Fax: +49 911 92885-33=20
GF: Julian Hein | AG N=FCrnberg HRB18461=20
=20
http://www.netways.de | [email protected]=20
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]