<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"> <META NAME="Generator" CONTENT="MS Exchange Server version 6.0.6617.47"> <TITLE>PRODUCTION and DEMO servers - config question</TITLE> </HEAD> <BODY>  Here is a common one I guess: I have zillions of servers and zillions of services. Some are PRODUCTION and some are DEMO/TEST. In general the same service exist on both PROD hosts and DEMO hosts. For this reason services are defined only once in the cfg file, e.g.: define service{ use generic-service host_name host1, host2, host3, host4 service_description my_service check_command bla bla } In the example you might think of host1 and host as PROD servers, while host3 and host4 are DEMO servers. My problem is that I want different notification setup for services on DEMO hosts as opposed to services on PROD hosts but I do not want to specify everything twice. How can I accomplish this without having to specify everything multiple times ? The first thing to note here is that in this scenario the notification setup is really an attribute on the host rather than on the service, i.e. in ideal world I would like Nagios to derive notification settings for service from the notification settings on the host on which it exist. A suggestion for how Nagios can be changed to accommodate this would be to add some functionality to the way the notifications_enabled settings on a service work. Currently: notifications_enabled : This directive is used to determine whether or not notifications for this service are enabled. Values: 0 = disable service notifications, 1 = enable service notifications. Suggested: notifications_enabled : This directive is used to determine whether or not notifications for this service are enabled. Values: 0 = disable service notifications, 1 = enable service notifications. 2 = derive setting from the host's notification setting (i.e. if host has notifications disabled then so will the service and vice versa). Any other ideas on this? Can you think of other ways of accomplishing the same ? I can see other mails in the archive on similar subject but I don't think a good solution has ever been found. rgds, Lars </BODY> </HTML>