Ok, admins is assigned to the "generic-service" service and to a "linux-server"
service as below. I'm still not sure as to why this is misbehaving.
define service{
name generic-service ; The 'name' of
this service template
active_checks_enabled 1 ; Active
service checks are enabled
passive_checks_enabled 1 ; Passive
service checks are enabled/accepted
parallelize_check 1 ; Active
service checks should be parallelized (disabling this can lead to major
performance problems)
obsess_over_service 1 ; We should
obsess over this service (if necessary)
check_freshness 0 ; Default is to
NOT check service 'freshness'
notifications_enabled 1 ; Service
notifications are enabled
event_handler_enabled 1 ; Service event
handler is enabled
flap_detection_enabled 1 ; Flap
detection is enabled
failure_prediction_enabled 1 ; Failure
prediction is enabled
process_perf_data 1 ; Process
performance data
retain_status_information 1 ; Retain status
information across program restarts
retain_nonstatus_information 1 ; Retain
non-status information across program restarts
is_volatile 0 ; The service
is not volatile
check_period 24x7 ; The service
can be checked at any time of the day
max_check_attempts 3 ; Re-check the
service up to 3 times in order to determine its final (hard) state
normal_check_interval 10 ; Check the
service every 10 minutes under normal conditions
retry_check_interval 2 ; Re-check the
service every two minutes until a hard state can be determined
contact_groups admins ; Notifications
get sent out to everyone in the 'admins' group
notification_options w,u,c,r ; Send
notifications about warning, unknown, critical, and recovery events
notification_interval 60 ; Re-notify
about service problems every hour
notification_period 24x7 ; Notifications
can be sent out at any time
register 0
}
define host{
name linux-server ; The name of this host
template
use generic-host ; This template
inherits other values from the generic-host template
check_period 24x7 ; By default, Linux
hosts are checked round the clock
check_interval 5 ; Actively check the
host every 5 minutes
retry_interval 1 ; Schedule host check
retries at 1 minute intervals
max_check_attempts 10 ; Check each Linux host
10 times (max)
check_command check-host-alive ; Default command to
check Linux hosts
notification_period workhours ; Linux admins hate to
be woken up, so we only notify during the day
; Note that the
notification_period variable is being overridden from
; the value that is
inherited from the generic-host template!
notification_interval 120 ; Resend notifications
every 2 hours
notification_options d,u,r ; Only send
notifications for specific host states
contact_groups admins ; Notifications get
sent to the admins by default
register 0
}
----- Original Message ----
From: Seth Simmons <[email protected]>
To: Grant Lowe <[email protected]>; nagios-user Mailinglist
<[email protected]>
Sent: Wednesday, December 17, 2008 12:35:30 PM
Subject: RE: [Nagios-users] Nagios Admin pages
No...the service definition itself.
define service{
use local-service
hostgroup_name Linux
service_description SSH
check_command check_ssh
max_check_attempts 2
check_interval 10
retry_interval 5
check_period 24x7
notification_interval 60
first_notification_delay 0
notification_period 24x7
contact_groups admins
notification_options c,w,r
}
-----Original Message-----
From: Grant Lowe [mailto:[email protected]]
Sent: Wednesday, December 17, 2008 3:34 PM
To: Seth Simmons; nagios-user Mailinglist
Subject: Re: [Nagios-users] Nagios Admin pages
Like this?
define contactgroup{
contactgroup_name admins
alias Nagios Administrators
members nagiosadmin
}
Please explain.
----- Original Message ----
From: Seth Simmons <[email protected]>
To: Grant Lowe <[email protected]>; nagios-user Mailinglist
<[email protected]>
Sent: Wednesday, December 17, 2008 11:35:53 AM
Subject: RE: [Nagios-users] Nagios Admin pages
Does the service/host specify 'contact_groups admins' in it?
-----Original Message-----
From: Grant Lowe [mailto:[email protected]]
Sent: Wednesday, December 17, 2008 2:28 PM
To: Seth Simmons; nagios-user Mailinglist
Subject: Re: [Nagios-users] Nagios Admin pages
The only two definitions that I have for nagiosadmin are these:
define contact{
contact_name nagiosadmin
; Short name of user
use generic-contact ;
Inherit default values from generic-contact template (defined above)
alias Nagios Admin ; Full
name of user
email [email protected]
}
and
define contactgroup{
contactgroup_name admins
alias Nagios Administrators
members nagiosadmin
}
----- Original Message ----
From: Seth Simmons <[email protected]>
To: Grant Lowe <[email protected]>; nagios-user Mailinglist
<[email protected]>
Sent: Wednesday, December 17, 2008 9:07:07 AM
Subject: RE: [Nagios-users] Nagios Admin pages
Does your service/host checks have nagiosadmin either defined as a
contact or part of a contact group?
-----Original Message-----
From: Grant Lowe [mailto:[email protected]]
Sent: Wednesday, December 17, 2008 10:24 AM
To: Seth Simmons; nagios-user Mailinglist
Subject: Re: [Nagios-users] Nagios Admin pages
Hi Seth,
I understand it better now. Thanks. But I'm still getting the
notifications as nagiosadmin. Any more ideas?
grant
----- Original Message ----
From: Seth Simmons <[email protected]>
To: Grant Lowe <[email protected]>; nagios-user Mailinglist
<[email protected]>
Sent: Tuesday, December 16, 2008 11:01:23 AM
Subject: RE: [Nagios-users] Nagios Admin pages
It's the other way around (assuming I'm understanding the question
correctly).
If you have a host defined and you tell it to use the generic-host
template and define a different parameter for that specific host, that
takes precedence.
For example, here is your generic-host template and a defined host.
define host{
name generic-host
notifications_enabled 1
event_handler_enabled 1
flap_detection_enabled 1
failure_prediction_enabled 1
process_perf_data 1
retain_status_information 1
retain_nonstatus_information 1
notification_period 24x7
register 0
}
define host{
name redhatserver
use generic-host
notifications_enabled 0
}
With the above host, it has notifications disabled; if that wasn't
defined for that host, it would use the value in the template.
Same applies for services.
-----Original Message-----
From: Grant Lowe [mailto:[email protected]]
Sent: Tuesday, December 16, 2008 1:32 PM
To: Seth Simmons; nagios-user Mailinglist
Subject: Re: [Nagios-users] Nagios Admin pages
Hi Seth,
Thanks for the link. I've looked more closely at the definitions, and
it looks like since I have the "generic" service that I'm using that
comes stalk with Nagios, that's what I'm using. That's what I'm
guessing anyway. This begets a question. If the other service
definitions "inherit" from the "generic" definition, it seems that the
"generic" service is the one that gets used, and has priority, not the
"inherited" one. Is that correct?
----- Original Message ----
From: Seth Simmons <[email protected]>
To: Grant Lowe <[email protected]>; nagios-user Mailinglist
<[email protected]>
Sent: Tuesday, December 16, 2008 9:08:21 AM
Subject: RE: [Nagios-users] Nagios Admin pages
start here
http://nagios.sourceforge.net/docs/3_0/notifications.html
-----Original Message-----
From: Grant Lowe [mailto:[email protected]]
Sent: Tuesday, December 16, 2008 11:51 AM
To: nagios-user Mailinglist
Subject: [Nagios-users] Nagios Admin pages
Hi All,
How do I get nagiosadmin to stop receiving notifications that the other
admins get? For example, the Windows guys get some that I don't need to
get.
Thanks for any pointers.
------------------------------------------------------------------------
------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas,
Nevada.
The future of the web can't happen without you. Join us at MIX09 to
help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.
com/
_______________________________________________
Nagios-users mailing list
[email protected]
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
------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you. Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
Nagios-users mailing list
[email protected]
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