Re: [Nagios-users] Elevated alerts
In the 'email' contact config, you need all the service notification
options: w,c,u,r,f,s
This is because you want warning and critical alerts sent to email.
In the 'paging' config, gid rid of the following lines:
host_notification_commandsnotify-host-by-pager
service_notification_commands notify-service-by-pager
# Added pager line 01/09/2009
pager gl...@pager.company.com
Then change the service notifications to: c,u,r,f,s
The way you have it now, the paging contact will not get critical alerts.
If your paging email address has a text username (glowe), you need to use
the notify-by-email arguments. If the user is numerical, then yes, you can
use the notify-by-pager commands. I mentioned this in my last email. I've
never researched it, for I've found that if I have a non-numerical user in
an email address and I use the notify-by-pager default CONTACTPAGER macro,
the notification is not sent.
James Moseley
Grant Lowe
To
jmose...@corp.xanadoo.com
01/10/2009 03:01 cc
PMnagios-users@lists.sourceforge.net
Subject
Re: [Nagios-users] Elevated alerts
define contact{
contact_name glowe1
alias Grant
contactgroups solaris-admins
host_notifications_enabled1
service_notifications_enabled 1
host_notification_period 24x7
service_notification_period 24x7
host_notification_options d,u,r,f,s,
service_notification_options w,u,r,f,s,
host_notification_commandsnotify-host-by-email
service_notification_commands notify-service-by-email
host_notification_commandsnotify-host-by-pager
service_notification_commands notify-service-by-pager
email gl...@pager.company.com
can_submit_commands 1
retain_status_information 0
retain_nonstatus_information 0
# Added pager line 01/09/2009
pager gl...@pager.company.com
}
--
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
___
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] Elevated alerts
On Jan 10, 2009, at 3:01 PM, Grant Lowe wrote:
> James,
>
> I've got the changes input as we've talked about. But I'm not
> getting pages. I searched the Nagios log and no pages. Any ideas?
> I'm at a loss to why. For what it's worth, here's my contact
> definitions:
>
> define contact{
> host_notification_options d,u,r
> service_notification_options w,u,r
What kind of notification are you expecting, a service critical? You
might need to determine the meaning of these two directives from the
documentation.
--
Marc
--
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
___
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] Elevated alerts
James,
I've got the changes input as we've talked about. But I'm not getting pages.
I searched the Nagios log and no pages. Any ideas? I'm at a loss to why. For
what it's worth, here's my contact definitions:
define contact{
contact_name glowe
alias Grant
contactgroups solaris-admins
host_notifications_enabled1
service_notifications_enabled 1
host_notification_period 24x7
service_notification_period 24x7
# Original line: host_notification_options d,u,r,f,s,
host_notification_options d,u,r
service_notification_options w,u,r
host_notification_commandsnotify-host-by-email
service_notification_commands notify-service-by-email
email gl...@company.com
can_submit_commands 1
retain_status_information 0
retain_nonstatus_information 0
}
define contact{
contact_name glowe1
alias Grant
contactgroups solaris-admins
host_notifications_enabled1
service_notifications_enabled 1
host_notification_period 24x7
service_notification_period 24x7
host_notification_options d,u,r,f,s,
service_notification_options w,u,r,f,s,
host_notification_commandsnotify-host-by-email
service_notification_commands notify-service-by-email
host_notification_commandsnotify-host-by-pager
service_notification_commands notify-service-by-pager
email gl...@pager.company.com
can_submit_commands 1
retain_status_information 0
retain_nonstatus_information 0
# Added pager line 01/09/2009
pager gl...@pager.company.com
}
- Original Message
From: "jmose...@corp.xanadoo.com"
To: Grant Lowe
Cc: nagios-users@lists.sourceforge.net
Sent: Friday, January 9, 2009 9:46:03 AM
Subject: Re: [Nagios-users] Elevated alerts
If the email address begins with a number, then use $CONTACTPAGER$ string.
I don't know exactly where those variables are defined, but when sending
email to an address that begins with a number (or perhaps contains an
all-numeric string before the @), I've found that the notification is not
sent if using a command definition that uses CONTACTEMAIL.
In the contacts config, use command definitions that have CONTACTEMAIL when
emailing a 'normal' email address. Use CONTACTPAGER when emailing a phone
or pager email address where the user string is numeric.
I'm sure the difference is explained in the documentation or mailling list
archives.
James Moseley
Grant Lowe
To
jmose...@corp.xanadoo.com
01/09/2009 11:30 cc
AMnagios-users@lists.sourceforge.net
Subject
Re: [Nagios-users] Elevated alerts
Ok. That helps. I'll replace the @MAIL_PROG@ with /bin/mail. Then where
is $CONTACTEMAIL$ defined, so I can add a new variable which I think will
be $CONTACTPAGER$, to replace the $CONTACTEMAIL$ in the command
definitions?
--
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
___
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
