Re: [Nagios-users] too much passive check status coming in
On 11/18/2010 03:11 AM, marc pascual wrote: On Thu, Nov 18, 2010 at 3:27 AM, Andreas Ericssona...@op5.se wrote: On 11/17/2010 08:11 PM, marc pascual wrote: Hello, I have too much passive checks coming in (12*880) to the point that some aren't getting processed by nagios. Now I've decided to rewrite the plugins so that it will only report state changes via nsca. (OK-to-CRIT and CRIT-to-OK). The problem I see with this move is that, if something temporarily hampers an nsca communication (e.g. transient high load, or temporary network blip), then there's no guaranteed way for nagios to know the real state of the service on the next check cycle. I wonder if anyone out there has implemented their checks similar to this, and what solutions or workarounds were implemented to make sure that nagios will eventually get updated with the correct states. You want freshness checks. Browse the nagios documentation for it and you'll find what you're looking for. Welcome to the list btw. It seems things finally worked out for you. But freshness checks imply that checks should be coming in at a regular interval (unless I'm mistaken). In this case, I don't have an idea when the next check result will come as I'm only sending results on state changes. Ah, right. In that case, check out Merlin. It replaces NSCA with a much faster protocol for transmitting check-data, and you get failover for free in case the poller node goes to lunch. http://www.op5.org/community/plugin-inventory/op5-projects/merlin -- Andreas Ericsson andreas.erics...@op5.se OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 Considering the successes of the wars on alcohol, poverty, drugs and terror, I think we should give some serious thought to declaring war on peace. -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today http://p.sf.net/sfu/msIE9-sfdev2dev ___ Nagios-users mailing list Nagios-users@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
[Nagios-users] too much passive check status coming in
Hello, I have too much passive checks coming in (12*880) to the point that some aren't getting processed by nagios. Now I've decided to rewrite the plugins so that it will only report state changes via nsca. (OK-to-CRIT and CRIT-to-OK). The problem I see with this move is that, if something temporarily hampers an nsca communication (e.g. transient high load, or temporary network blip), then there's no guaranteed way for nagios to know the real state of the service on the next check cycle. I wonder if anyone out there has implemented their checks similar to this, and what solutions or workarounds were implemented to make sure that nagios will eventually get updated with the correct states. Thank you, Marc -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today http://p.sf.net/sfu/msIE9-sfdev2dev___ Nagios-users mailing list Nagios-users@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
Re: [Nagios-users] too much passive check status coming in
On 11/17/2010 08:11 PM, marc pascual wrote: Hello, I have too much passive checks coming in (12*880) to the point that some aren't getting processed by nagios. Now I've decided to rewrite the plugins so that it will only report state changes via nsca. (OK-to-CRIT and CRIT-to-OK). The problem I see with this move is that, if something temporarily hampers an nsca communication (e.g. transient high load, or temporary network blip), then there's no guaranteed way for nagios to know the real state of the service on the next check cycle. I wonder if anyone out there has implemented their checks similar to this, and what solutions or workarounds were implemented to make sure that nagios will eventually get updated with the correct states. You want freshness checks. Browse the nagios documentation for it and you'll find what you're looking for. Welcome to the list btw. It seems things finally worked out for you. -- Andreas Ericsson andreas.erics...@op5.se OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 Considering the successes of the wars on alcohol, poverty, drugs and terror, I think we should give some serious thought to declaring war on peace. -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today http://p.sf.net/sfu/msIE9-sfdev2dev ___ Nagios-users mailing list Nagios-users@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
Re: [Nagios-users] too much passive check status coming in
On Thu, Nov 18, 2010 at 3:27 AM, Andreas Ericsson a...@op5.se wrote: On 11/17/2010 08:11 PM, marc pascual wrote: Hello, I have too much passive checks coming in (12*880) to the point that some aren't getting processed by nagios. Now I've decided to rewrite the plugins so that it will only report state changes via nsca. (OK-to-CRIT and CRIT-to-OK). The problem I see with this move is that, if something temporarily hampers an nsca communication (e.g. transient high load, or temporary network blip), then there's no guaranteed way for nagios to know the real state of the service on the next check cycle. I wonder if anyone out there has implemented their checks similar to this, and what solutions or workarounds were implemented to make sure that nagios will eventually get updated with the correct states. You want freshness checks. Browse the nagios documentation for it and you'll find what you're looking for. Welcome to the list btw. It seems things finally worked out for you. But freshness checks imply that checks should be coming in at a regular interval (unless I'm mistaken). In this case, I don't have an idea when the next check result will come as I'm only sending results on state changes. (Thanks for the help earlier/yesterday, I had to re-resubscribe my email address with the dots in it) Marc -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today http://p.sf.net/sfu/msIE9-sfdev2dev___ Nagios-users mailing list Nagios-users@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
