On 10/02/2012 11:38 AM, Marco Borsani wrote: > Hi all > > > > I would modify $SERVICEDESC$ before Nagios use it to send notification. > > Due internal procedure I can’t modify the “service description” inside our > configuration file. > > > > For example $SERVICEDESC$ is “aaaaa_bbbbb_check_tcp_port_1234” I would > change it in “tcp_port_1234” (“just” cut N-char at the beginning of the > string) > > How can I do this ? >
Wrap notifications in a script of your own and cut as much as you like from whatever you like. There's no sensible way to do it from inside Nagios, since that will have ramifications for modules and everything else. Notifications are (normally) not so frequent that wrapping them in an extra layer of execution will matter. -- Andreas Ericsson andreas.erics...@op5.se OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 Considering the successes of the wars on alcohol, poverty, drugs and terror, I think we should give some serious thought to declaring war on peace. ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ 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