Re: [CentOS] Somewhat OT: (Nagios)
On Wed, 14 May 2008, Thomas Harold wrote: Oh, and SELinux will probably get in your way. There's an understatement. :-) Nagios needs to do so many things, that devising a decent policy for it is tear-your-hair-out hard. It's also a moving target if you, like me, want to add tests for every new host/service that goes into production. -- Paul Heinlein <> [EMAIL PROTECTED] <> http://www.madboa.com/ ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: Using Nagios in CentOS (It was Re: [CentOS] Somewhat OT: (Nagios))
> Really, thanks all for your experiences. Bear in mind that what I want > to do is (mainly) monitor network switches, and get data and charts > of them. I hope I can do that. > > Keep in touch > > -- Hi, I have a problem with check_snmp plugin, it outputs: [1210863277] SERVICE ALERT: sw1;Uptime;UNKNOWN;SOFT;1;SNMP problem - No data received from host I've tried to run on command-line /usr/lib64/nagios/plugins/check_snmp -H 10.1.0.3 -o .1.3.6.1.2.1.1.3.0 -C "p" -m -P 2c SNMP problem - No data received from host CMD: /usr/bin/snmpget -t 1 -r 5 -m -v 2c [authpriv] 10.1.0.3:161 .1.3.6.1.2.1.1.3.0 snmp packages are installed -- -- Open Kairos http://www.openkairos.com Watch More TV http://sebelk.blogspot.com Sergio Belkin - ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Using Nagios in CentOS (It was Re: [CentOS] Somewhat OT: (Nagios))
2008/5/14 Thomas Harold <[EMAIL PROTECTED]>:
> Sergio Belkin wrote:
>>
>> 2008/5/13 <[EMAIL PROTECTED]>:
>>
>> OK, you won :) I'm going to test nagios. I am using centos 5.1
>> x86_64. Do I lose much if I use rpm from rpmforge (version 2.9)?
>>
>
> We're running version 2.11 at the office (on CentOS 5.1 x86_64). I've
> looked at some of the things in 3.0, but there's nothing there that I needed
> yet.
>
> Hopefully you have some way to track changes in /etc/nagios (FSVS is what we
> use), because it will make your life much easier to have an audit trail.
>
> We created sub-folders under /etc/nagios to hold the various types of
> entities. For example, we have:
>
> /etc/nagios/commands
> /etc/nagios/contacts
> /etc/nagios/contactgroups
> /etc/nagios/hosts-switches
> /etc/nagios/hosts-dmz
> /etc/nagios/hosts-servers
> /etc/nagios/hosts-lan
> /etc/nagios/templates-hosts
> /etc/nagios/templates-services
>
> We then broke individual elements out of the default massive configuration
> folder into individual .cfg files. For example, we chose to create
> individual files for each contact rather the putting them all in a single
> file. So far it works well, it's a lot easier to get a feel for what users
> have been defined, what hosts are defined, what the templates are. Because
> when I look in templates-services, I see from the directory listing that I
> have service templates named X, Y and Z (without having to open up the file
> to look).
>
> We currently put service checks for individual hosts in the same
> configuration file as the host. So you will have the following definitions
> in a typical host file (until you get into templating):
>
> define host{
> define hostextinfo{
> define service{
> define service{
> ...
>
> Any plugins that we wrote ourself, we put under a separate folder. Which
> keeps them separate from
>
> /usr/local/lib64/nagios-plugins/
>
> Basically, start small, track your changes, and plan on refactoring it in
> week #2 after you start monitoring about a dozen hosts. Stay away from
> advanced things like escalation, monitoring things like disk space on remote
> servers, or the like until you get the basics working.
>
> Oh, and SELinux will probably get in your way. So you'll need to play with
> audit2allow to create supplemental policy to give Nagios additional
> permissions. (Which may have been due to PEBKAC issues on my end - I plan
> on going back and looking at labeling and figuring out what I mislabeled.)
>
> I think that's the majority of the issues that we dealt with in the past 2
> weeks. We're now in fine-tuning mode and getting ready to start monitoring
> remote services next week.
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>
Really, thanks all for your experiences. Bear in mind that what I want
to do is (mainly) monitor network switches, and get data and charts
of them. I hope I can do that.
Keep in touch
--
--
Open Kairos http://www.openkairos.com
Watch More TV http://sebelk.blogspot.com
Sergio Belkin -
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Somewhat OT: (Nagios)
Sergio Belkin wrote:
2008/5/13 <[EMAIL PROTECTED]>:
OK, you won :) I'm going to test nagios. I am using centos 5.1
x86_64. Do I lose much if I use rpm from rpmforge (version 2.9)?
We're running version 2.11 at the office (on CentOS 5.1 x86_64). I've
looked at some of the things in 3.0, but there's nothing there that I
needed yet.
Hopefully you have some way to track changes in /etc/nagios (FSVS is
what we use), because it will make your life much easier to have an
audit trail.
We created sub-folders under /etc/nagios to hold the various types of
entities. For example, we have:
/etc/nagios/commands
/etc/nagios/contacts
/etc/nagios/contactgroups
/etc/nagios/hosts-switches
/etc/nagios/hosts-dmz
/etc/nagios/hosts-servers
/etc/nagios/hosts-lan
/etc/nagios/templates-hosts
/etc/nagios/templates-services
We then broke individual elements out of the default massive
configuration folder into individual .cfg files. For example, we chose
to create individual files for each contact rather the putting them all
in a single file. So far it works well, it's a lot easier to get a feel
for what users have been defined, what hosts are defined, what the
templates are. Because when I look in templates-services, I see from
the directory listing that I have service templates named X, Y and Z
(without having to open up the file to look).
We currently put service checks for individual hosts in the same
configuration file as the host. So you will have the following
definitions in a typical host file (until you get into templating):
define host{
define hostextinfo{
define service{
define service{
...
Any plugins that we wrote ourself, we put under a separate folder.
Which keeps them separate from
/usr/local/lib64/nagios-plugins/
Basically, start small, track your changes, and plan on refactoring it
in week #2 after you start monitoring about a dozen hosts. Stay away
from advanced things like escalation, monitoring things like disk space
on remote servers, or the like until you get the basics working.
Oh, and SELinux will probably get in your way. So you'll need to play
with audit2allow to create supplemental policy to give Nagios additional
permissions. (Which may have been due to PEBKAC issues on my end - I
plan on going back and looking at labeling and figuring out what I
mislabeled.)
I think that's the majority of the issues that we dealt with in the past
2 weeks. We're now in fine-tuning mode and getting ready to start
monitoring remote services next week.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
