search

kafelez / jsendnsca

Automatically exported from code.google.com/p/jsendnsca
0 stars 0 forks source link

Implement a non-blocking NagiosPassiveCheckSender #11

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Often, a non-blocking sender is preferable so that when sending passive
checks, your main applications threads are not blocking, especially when
there are network issues slowing down delivery of passive checks to NSCA.

This is especially important if NSCA is slow or your requests are timing
out. With a non-blocking NagiosPassiveCheckSender, it can implement
internal queuing and a retry strategy, freeing up you application to carry
on processing.

If after a retry strategy is employed and the request stills fail, an
alternative action can be taken i.e. logging to a file.

Original issue reported on code.google.com by rajneeshpatel on 12 Feb 2009 at 10:17

GoogleCodeExporter commented 8 years ago 
Implemented in 1.2

Original comment by rajneeshpatel on 3 May 2009 at 12:19