Technically, I can patch the source in hours. The problem is, I don't want to patch others' project unless the project is dead. I am sure you guys are still working on the project and the software will be upgraded soon, rit... Just want to let you know what people may need from nagios..... I think that some software like nagios, should focus on large network or middle size network. Since if I have only one server or two, we don't really need a too complicate monitor system. Actually, just some plug-ins which nagios used, like check_ping, check_tcp, check_udp can do the job..... BTW, use nagios, our main purpose is: notify the customer on time if a server/serivce is down so they know it and then they will decide what to do. We just notify them and that's it. So notificiation is the most important job since customers want to be the first to know if their server/services are down. We have many other monitor systems already running in our network. And testing nagios now since it has many great features. Thanks for the great software! regards, Billow <div>On 10/20/05, Andreas Ericsson <<a href="mailto:ae@op5.se">ae@op5.se</a>> wrote:<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Billow Gao wrote: > I am talking about an ISP here. > Those server admin are not ours, but customers'. > Are those customers likely to have the required access to fix the problems that may arise? If not, you may want to skip sending them email and just get them a cronscript-generated availability report every month or so. Or if you're really sensible, you'll get that report when it's showing good figures and the customers is disputing the SLA. > 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. > So? Charge a little something for that service and buy the server-park you need to do the job. It's the whole idea behind the term "business" after all. > 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 <a href="mailto:myemail@domain.com"> myemail@domain.com</a> > The greatest thing about opensource software is that if you need it to do something that it currently doesn't, you can simply change it. I'm sure Ethan would gladly accept a patch for this. If, for some reason, you are unable to produce one yourself I'd be happy to help. Given the amount of customers you have I'm sure you'd be satisfied with paying quite a large sum of money to get this problem sorted out. If so, I'm your man. It's about 16 hours worth of coding, testing included. > 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 <<a href="mailto:Andrew.Laden@tudor.com">Andrew.Laden@tudor.com </a>> 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. <a href="http://solutions.newsforge.com/ibmarch.tmpl">http://solutions.newsforge.com/ibmarch.tmpl </a> >>_______________________________________________ >>Nagios-users mailing list >><a href="mailto:Nagios-users@lists.sourceforge.net">Nagios-users@lists.sourceforge.net</a> >><a href="https://lists.sourceforge.net/lists/listinfo/nagios-users"> https://lists.sourceforge.net/lists/listinfo/nagios-users</a> >>::: Please include Nagios version, plugin version (-v) and OS when >>reporting any issue. >>::: Messages without supporting info will risk being sent to /dev/null >> > > -- Andreas Ericsson <a href="mailto:andreas.ericsson@op5.se">andreas.ericsson@op5.se</a> OP5 AB <a href="http://www.op5.se">www.op5.se</a> Tel: +46 8-230225 Fax: +46 8-230231 ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. <a href="http://solutions.newsforge.com/ibmarch.tmpl"> http://solutions.newsforge.com/ibmarch.tmpl</a> _______________________________________________ Nagios-users mailing list <a href="mailto:Nagios-users@lists.sourceforge.net">Nagios-users@lists.sourceforge.net</a> <a href="https://lists.sourceforge.net/lists/listinfo/nagios-users">https://lists.sourceforge.net/lists/listinfo/nagios-users</a> ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null </blockquote></div>