Hallo,
my problem:
I ve several notebooks without regular contact to my nagios-system. It
could happen that they are 4 weeks on the road.
I m looking for a way to collect informations like CPU-Load,
smartmon-informations and themperatures and to store them local on the
notebook.
If a
Hello All
In the last couple of weeks i noticed an odd occurrence in the output of
the check_procs on my master Nagios server
the default command : check_local_procs , gives out the following output :
WARNING;PROCS WARNING: 380 processes with STATE = RSZDT
Although when executing the command
Greetings,
I tried updating my (perfectly working, mind you) ndoutils from
1.4b7 to 1.4b9 over the weekend and was primarily rewarded with
segfaults and other grief which has resisted investigation and
fixes. The errors were introduced in 1.4b8 and persist into 1.4b9.
I'm running on
prengel wrote:
Hallo,
my problem:
I ve several notebooks without regular contact to my nagios-system. It
could happen that they are 4 weeks on the road.
I m looking for a way to collect informations like CPU-Load,
smartmon-informations and themperatures and to store them local on the
hey gang,
I'm trying to get a sense of what's normal for the number of checks per
host.
I'm pushing nagios to a number of servers and the list of things I want to
monitor keeps growing.
For some servers, I've got 30 checks - some 50.
what is normal out there?
is there a practical limit?
I'm trying to get a sense of what's normal for the number of checks per
host.
If you had a data set of information on Nagios installations you may
find an average service checks/hosts ratio but I don't really
understand the purpose. People are going to want to monitor different
things and at
apparently nagios notifications stopped being mailed by nagios@ and started
being mailed by postmaster@ when we upgraded from 3.2.0 to 3.2.1. is there
a way to get that back to nag...@?
--
This SF.net email is sponsored
On Mon, Jul 12, 2010 at 1:39 PM, Joel Brooks jbro...@oddelement.com wrote:
hey gang,
I'm trying to get a sense of what's normal for the number of checks per
host.
I'm pushing nagios to a number of servers and the list of things I want to
monitor keeps growing.
For some servers, I've got
As pointed out, normal depends on your environment. Some sites only
check a handful
of things per host; some check more. The bigger issue is if your
server can handle
the number of checks and in a timely fashion. Look at nagios parameters
Max_service_check_spread,
max_host_check_spread
as well as
Thanks guys.
I'm not so worried about the monitoring server. It has lots of head room,
and/but I will continue to monitor that.
I was mainly interested to know about people's experiences using nagios with
a lot of checks per host in terms of usability (web interface),
configuration, etc.
i.e.
On 12 July 2010 18:39, Joel Brooks jbro...@oddelement.com wrote:
hey gang,
I'm trying to get a sense of what's normal for the number of checks per
host.
I'm pushing nagios to a number of servers and the list of things I want to
monitor keeps growing.
For some servers, I've got 30 checks
Hi All,
My understanding is that when there's a schedule downtime for a host,
there should be no notification sent out for all services for that host.
In our setup, we get notification for a service down during the host
schedule downtime period because it looks like that the check result of
that
12 matches
Mail list logo