How do you handle odd contacts?
Furnish, Trever G
TGFurnish at herff-jones.com
Wed Jun 25 19:21:54 CEST 2003
Actually although that sounds like a solution at first glance, I don't think
it is.
My services currently apply to host groups based on function (not
geography). For example, telnet applies to Unix servers, dns applies to DNS
servers. If I were to do as you suggest, then I would have to apply the
service separately twice - once to her Unix server with her contact group
listed, and once to all the other Unix servers without her contact group
listed.
That's a bad solution for at least these reasons:
- Multiplies by many times the number of host groups I have.
- Multiplies by many times the number of services definitiongs I
have.
- Completely hoses both the status grid and the overview pages.
(Since host grouping is effectively gone.)
So I'm back to thinking that although contact and host grouping are nice
features, they aren't a replacement for being able to assign a single
contact to a hosts, hostgroups, and services directly using the contact
object itself.
Hopefully I'm just misunderstanding - keep working on me. :-)
-t.
-----Original Message-----
From: Marc Powell [mailto:mpowell at ena.com]
Sent: Wednesday, June 25, 2003 11:28 AM
To: Furnish, Trever G; Nagios-Users List (E-mail)
Subject: RE: [Nagios-users] How do you handle odd contacts?
Services are easy --
contact_groups: This is a list of the short names of the contact groups
that should be notified whenever there are problems (or recoveries) with
this service. Multiple contact groups should be separated by commas.
Just create a contact_group with her as the only member and for each
service that she should be notified for add her contact_group to what
you already have there. Nagios was designed this way I assume to allow
for the greatest flexibility in contact configurations.
For the hosts, you will need to create a new hostgroup that contains the
hosts that she should be notified for with her contact_group as the
contact. Don't worry that the hosts are defined in another hostgroup as
well, it's no big deal. If you use authentication then only she will see
the new hostgroup.
--
Marc
> -----Original Message-----
> From: Furnish, Trever G [mailto:TGFurnish at herff-jones.com]
> Sent: Wednesday, June 25, 2003 11:12 AM
> To: Nagios-Users List (E-mail)
>
> I'm in a quandry. I have my hosts and services and contacts nicely
laid
> out
> in a functional way (unix servers, windows servers, routers, switches,
> dns,
> etc) that fits nicely with the job responsibilities of the people who
> normally respond to outages - but now I have one remote admin at one
site
> who would like to receive alerts only when one of her systems is down.
>
> The problem is that in order to send her alerts concerning only her
> systems
> (one unix box, one windows box), I think I would have to remove her
hosts
> from their logical groups and create additional groups (host and
contact)
> for just those systems. That seems like a really bad solution - all I
> want
> is to allow a contact to get alerts regarding a specific device,
without
> screwing up the logical layout of the rest of the config file.
>
> Am I missing something? Is there a way to "apply a contact to a host
or
> service" instead of the other way around? How do you handle this at
your
> site?
>
> It seems like the way Nagios handles the connections between contacts
and
> hosts and services is only partially complete. Specificly, I can
apply a
> contact group to a hostgroup or a service, but I can't apply a contact
(no
> "group") to it. Nor can I apply a contact or contact group to a
single
> host. It's nice that grouping is available, but it's not so nice that
> grouping is *required*. :-(
>
> I've been using the template files for several years now but I admit
it
> still gives me a headache when I think about it - if I'm missing
something
> I'd love any advice.
>
> I think the situation I have is probably similar to that in lots of
> companies with big branch offices. I have a core operations team at a
> central head quarters office, but I also have branch offices that
usually
> have one or more local admins. The local admins should only get
alerts
> related to their devices (in other words, based on geography); the
> headquarters operations team should get alerts based on their area of
> expertise (unix, windows, routers, etc).
>
> The only way I can see to satisfy my requirements is to put every host
> into
> its own hostgroup, just because I can't apply a single contact to a
single
> host or service. What am I missing?
>
> --
> Trever
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: INetU
> Attention Web Developers & Consultants: Become An INetU Hosting
Partner.
> Refer Dedicated Servers. We Manage Them. You Get 10% Monthly
Commission!
> INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
> _______________________________________________
> Nagios-users mailing list
> Nagios-users at 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
-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
_______________________________________________
Nagios-users mailing list
Nagios-users at 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
More information about the Users
mailing list