Re: [Nagios-users] What kind of checks/minute numbers are you getting for single host / non-distributed setups?
Hi Ryan, On Fri, Aug 28, 2009 at 11:31 PM, Ryan Bowlby wrote: > Those are impressive numbers for a single Nagios instance. You may be able to > tweak out some additional time but you leave the Nagios daemon little room > for leeway. What I mean is if two dozen hosts start reporting critical and > Nagios starts performing checks at the more aggressive retry_check_interval > instead of the normal check_interval, then your check latency is going to go > through the roof. Yes, we have had to balance that already and good point, right now the majority of our service checks have a 5 normal / 3 retry with 2 retries which has been fine for our users. > That being said here are some ideas that you may already be trying, but if > not may by you some time. > - switch from check_ping to check_icmp as it's 9x faster in some instances. We did that, and yes, definitely a noticable improvement there. > - If any of the client-side nrpe checks are perl, python, etc you may see a > decrease in check-time by compiling them. Same for the Nagios server if you > aren't already (built-in perl, etc). All of our checks are either C plugins or ePN-based perl checks :). > - Often NRPE checks such as those monitoring hardware don't need to be > performed as often as say a check_tcp, but since people use templates NRPE > frequently gets configured with the same aggressive check_interval as other > checks. Scaling back on these will greatly increase the amount of checks the > server can do. Our retry is pretty conservative (60% of normal), good point though, should see if anyone has configured their checks to have a more aggressive retry rate (we work on a self-service model where users of our system can modify their own configs). > At my work we have 4 remote Nagios instances performing approximately 9400+ > checks to our Central Nagios server via nsca. This leaves room for a 400% > increase in checks as more departments begin utilizing the monitoring system. > Our configs are built by a custom script from our custom dbase and pushed out > to the servers via a custom script that keeps everything in cvs. It all works > great but took forever to configure. If I had to do it again I would take a > serious look at two other options: Very nice. > http://dnx.sourceforge.net/ - Crap ton of checks ONE nagios instance! We are going to try this first for our poller tier and keep notifications, trending, and trap persistence on a separate tier. Only concern here is that the remote pollers will not have ePN and I know how much CPU and load will increase running thousands of checks a minute in perl without ePN We have been playing (at the whiteboard level) with the idea of a persistent script execution proxy/daemon that would allow us to develop scripts in VHLL languages and the scripts would then be called with a check command like check_nrpe that just knows how to talk to the persistent script daemon over a socket .. so, for example, we could write something based on a JVM that embedded jruby and jython as well, allowing developers to write checks in java, ruby, or python. This would also eliminate the problem of having to always do full restarts of Nagios when ePN is on .. we realize this would not be an easy thing to implement, but it sounds theoretically very attractive as a way to allow for decent check performance and abstract the persistent language daemon outside of Nagios. > http://www.opsview.org/ - Multiple Nagios instances without writing a slew of > custom scripts to do it! That is definitely well known for performing well and it's stability :). Thanks a lot for responding, Ryan, appreciate it! - Max -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ 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] check_http confusion / problem
Jon Angliss wrote: > On Fri, 28 Aug 2009 14:01:44 -0500, "David Dyer-Bennet" > wrote: > > >> [check_http questions] >> > > --help usually gives a whole bunch of extra information... > > Yes, that's where I got the information I had; it's what got me confused in the first place. In particular, help shows a long-form as well as a short-form option for -e, and it was while discovering that the long-form option given in help doesn't appear to be recognized that I ended up with the "-e=400" syntax which is wrong (but which IS accepted). >> [...@prcapp00 dev]$ /usr/lib/nagios/plugins/check_http >> --IP-address=192.168.5.3 -p 8075 --no-body -f critical -v -v -v -e="Bad >> Request" >> GET / HTTP/1.0 >> User-Agent: check_http/1.99 (nagios-plugins 1.4.6) >> >> >> http://192.168.5.3:8075/ is 168 characters >> STATUS: HTTP/1.1 400 Bad Request >> HEADER >> Content-Type: text/html >> Date: Fri, 28 Aug 2009 18:33:44 GMT >> Connection: close >> Content-Length: 39 >> CONTENT >> [[ skipped ]] >> Invalid HTTP response received from host on port 8075 >> [...@prcapp00 dev]$ echo $? >> 2 >> > > Command syntax is incorrect. > > # ./check_http -I 192.168.5.3 -p 8075 --no-body -f critical -vvv -e \ > "Bad Request" > That was the base problem in some sense, thanks. > I tried against one of my servers without any issues. Albeit I got a > critical failure because my server didn't return bad request. > > I do notice you're using an old version of the plugins package. 1.4.13 > is the current version, can you download and compile in a different > directory and see if you still end upw with the same issue? > This is a Centos 4.7 install, and I'm trying to stick to the packaged distributions that match each other, rather than going around upgrading things at random and hoping they work together. -- David Dyer-Bennet, d...@dd-b.net; http://dd-b.net/ Snapshots: http://dd-b.net/dd-b/SnapshotAlbum/data/ Photos: http://dd-b.net/photography/gallery/ Dragaera: http://dragaera.info -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ 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] hostgroup expansion and regex
On Sat, Aug 29, 2009 at 4:22 AM, Jim Avery wrote:
> 2009/8/29 Terry :
>> I am overlooking something simple.
>> Nagios Core 3.2.0
>>
>> use_regexp_matching=1
>> use_true_regexp_matching=0
>>
>> define hostgroup {
>> hostgroup_name allhosts
>> members *
>>
>> Error: Could not expand members specified in hostgroup (config file
>> '/etc/nagios/objects/hostgroups.cfg', starting on line 89)
>>
>> What in the world am I missing here?
>
>
> "*" is a wildcard, not a regular expression. To use simple wildcards
> like this you need:
>
> use_regexp_matching=0
>
>
> If you still want to use a regular expression though, the one you need
> which would be equivalent to a "*" wildcard is:
>
> .*
>
> The "." means "match any character" and the "*" in a regular
> expression means "match zero or more repetitions of the previous
> element.".
>
>
> hth,
>
> Jim
>
> --
I tried .* with regex and true_regex but I clearly didnt try * without
enable_regex. Thanks for helping!
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
___
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] Redundant Nagios setups...
2009/8/26 Janet Sullivan : > Other than the methods described in the official docs > (http://nagios.sourceforge.net/docs/3_0/redundancy.html) and Merlin > (http://www.op5.org/community/projects/merlin) are there any other suggested > solutions for setting up redundant Nagios servers? > For HA we use a Xen domU that can jump between 2 physical hosts... Regards, -- Ciro Iriarte http://cyruspy.wordpress.com -- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ 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] hostgroup expansion and regex
2009/8/29 Terry :
> I am overlooking something simple.
> Nagios Core 3.2.0
>
> use_regexp_matching=1
> use_true_regexp_matching=0
>
> define hostgroup {
> hostgroup_name allhosts
> members *
>
> Error: Could not expand members specified in hostgroup (config file
> '/etc/nagios/objects/hostgroups.cfg', starting on line 89)
>
> What in the world am I missing here?
"*" is a wildcard, not a regular expression. To use simple wildcards
like this you need:
use_regexp_matching=0
If you still want to use a regular expression though, the one you need
which would be equivalent to a "*" wildcard is:
.*
The "." means "match any character" and the "*" in a regular
expression means "match zero or more repetitions of the previous
element.".
hth,
Jim
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
___
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
