Suggestion about new field in Service Object

[Billow Gao]

I am talking about an ISP here.
Those server admin are not ours, but customers'.

And we just provide a center nagios server for them to monite their servers.

So there will be thousands of servers/services need to be added into nagios.

And we cann't use mailling list since different servers/services belong to
different person.
I already reduced the size of contact to four lines so totally 10 lines for
a new email address. (The other options are the same and in the template:
customer-contact)

=====================
define contact{
use customer-contact
contact_name contact_name
alias contact_alias
email contact_email_address
}

define contactgroup{
contactgroup_name contactgroup_name
alias contactgroup_alias
members contact_name
}
=====================


Just wonder why not provide a service-alias field in Service object and then
we can just use one line:
service_alias myemail at domain.com

and then use a command like:
define command{
command_name notify-by-email
command_line /usr/bin/printf "%b" "***** Nagios *****\n\nNotification Type:
$NOTIFICATIONTYPE$\n\nService: $SERVICEDESC$\nHost: $HOSTALIAS$\nAddress:
$HOSTADDRESS$\nState: $SERVICESTATE$\n\nDate/Time:
$LONGDATETIME$\n\nAdditional Info:\n\n$SERVICEOUTPUT$" | /bin/mail -s "**
$NOTIFICATIONTYPE$ alert - $HOSTALIAS$/$SERVICEDESC$ is $SERVICESTATE$ **"
$SERVICE_ALIAS$
}

Also, one server can have many IPs, and different service may use different
IP in the same server.
We have to create new check commands and pass the IP directly to the command
like:
command_line $USER1$/check_tcp -H $ARG1$ -p $ARG2$
So we don't need to create a host obejct for each IP.

Just a suggestion.....


Thanks

Ying






On 10/20/05, Andrew Laden <Andrew.Laden at tudor.com> wrote:
>
> I cant speak for what he is doing, but I have considered making a
> "subscription" based notification. Make an email address for each
> individual
> item that is being monitored. That email address is actually a mailing
> list.
> That way, users who are interested in getting alerts for a particular item
> can just add themselves to the mailing list. I don't have to update the
> contactgroups config file. I can auto generate it based on the hosts and
> services.
>
> That could easily make a lot of email addresses, with very little work to
> configure.
>
> Not that I am doing this currently, But I have been in places that did
> this
> sort of thing.
>
> -Andrew
>
>
>
>
> > > For example: For notification, since most of our services are using
> > > the same format of notification, just different email address.
> > > There will be thousands of different email address. And we have to
> > > create a contact object and a contact group for every
> > single email address.
> >
> > A nagios installation with thousands of different
> > email-addresses? Are you quite sure that there is, literally,
> > thousands of people actually administrating your network? If
> > so, you have much worse problems than Nagios taking half a
> > day to load its configuration.
> >
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Power Architecture Resource Center: Free content, downloads, discussions,
> and more. http://solutions.newsforge.com/ibmarch.tmpl
> _______________________________________________
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20051020/3eb8a86d/attachment.html>