Was: Nagios arch to improve performance Re: [Nagios-devel] Re: Nagios-devel digest, Vol 1 #807 - 8 msgs
Posted: Mon May 23, 2005 1:27 am
This is a multi-part message in MIME format...
------------=_1116840399-58553-166
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Dear Folks,
I am writing to thank you for an interesting and informative thread
(the code examples were about the right length/complexity for my
strictly limited C-fu [s/C/any_language/]; I much prefer people to post
code rather than HTML/Base 64/... and it is really good to see
benchmarks of alternative proposals. Andreas++, Sean++).
Nagios scales pretty darn will despite the limitations of fork/exec().
There is one Nag 2.x user with ~ 15k services, whose check latencies
hover around 25 seconds (I have asked permission to release the
details and will do so if possible) with an active service check profile
of
1 check_ping @ 5 min intervals
2 custom checks of perf data (RAM/cycles/etc (SNMP + RRD ?)
@ 15 min intervals
3 file system checks (SNMP ?) @ 60 min intervals
Since this number of service checks are handled Ok (in this isolated
knowledgable-user case) and those checking much more services are going
to be under heavy PHB pressure to buy a name brand product, is this
worth pursuing ?
That said, if my reference implementation of all sorts of useful
techniques adds a few more, Good.
Yours sincerely.
--
Stanley Hopcroft
------------=_1116840399-58553-166
Content-Type: text/plain; name="disclaimer.txt"
Content-Disposition: inline; filename="disclaimer.txt"
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0
X-Mailer: MIME-tools 5.415 (Entity 5.415)
--
This message contains privileged and confidential information only
for use by the intended recipient. If you are not the intended
recipient of this message, you must not disseminate, copy or use
it in any manner. If you have received this message in error,
please advise the sender by reply e-mail. Please ensure all
e-mail attachments are scanned for viruses prior to opening or
using.
------------=_1116840399-58553-166--
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]
------------=_1116840399-58553-166
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Dear Folks,
I am writing to thank you for an interesting and informative thread
(the code examples were about the right length/complexity for my
strictly limited C-fu [s/C/any_language/]; I much prefer people to post
code rather than HTML/Base 64/... and it is really good to see
benchmarks of alternative proposals. Andreas++, Sean++).
Nagios scales pretty darn will despite the limitations of fork/exec().
There is one Nag 2.x user with ~ 15k services, whose check latencies
hover around 25 seconds (I have asked permission to release the
details and will do so if possible) with an active service check profile
of
1 check_ping @ 5 min intervals
2 custom checks of perf data (RAM/cycles/etc (SNMP + RRD ?)
@ 15 min intervals
3 file system checks (SNMP ?) @ 60 min intervals
Since this number of service checks are handled Ok (in this isolated
knowledgable-user case) and those checking much more services are going
to be under heavy PHB pressure to buy a name brand product, is this
worth pursuing ?
That said, if my reference implementation of all sorts of useful
techniques adds a few more, Good.
Yours sincerely.
--
Stanley Hopcroft
------------=_1116840399-58553-166
Content-Type: text/plain; name="disclaimer.txt"
Content-Disposition: inline; filename="disclaimer.txt"
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0
X-Mailer: MIME-tools 5.415 (Entity 5.415)
--
This message contains privileged and confidential information only
for use by the intended recipient. If you are not the intended
recipient of this message, you must not disseminate, copy or use
it in any manner. If you have received this message in error,
please advise the sender by reply e-mail. Please ensure all
e-mail attachments are scanned for viruses prior to opening or
using.
------------=_1116840399-58553-166--
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]