Nagios Support Forum

Contact Inheritance - According to the documentation, contacts should only be inherited from host to service if the service has no other contacts whatsoever (and the same goes for escalations), but the way the code previously worked was that it handled contact_groups and contacts directives separately, meaning services with only 'contacts' specified were still eligible for inheriting 'contact_groups' from the host. This has been updated to comply with the documentation.

• Assigned at the object level
• Only runs on-state-change
• Host and Services have their own macros
• Not all Nagios macros are available to event handlers
• Need to interpret object-type
• Need to interpret downtime-depth
• Need to interpret state
• Need to interpret state-type
• Requires guarding against check volatility

• Assigned at the contact level
• Separate command for hosts and services
• Uses object notification settings
• Provides path for escalation
• Notification specific Nagios macros
• Some object level macros are available to notification commands

logisbk wrote: ↑Tue Apr 07, 2026 7:48 am Below is the host notification command provided by our ITSM software:

Code: Select all

curl -X POST -H "Authorization: {Use Password token here without these brackets}" -H "Content-Type: application/json" --data "{"metric_name": "Availability", "hostname": "$HOSTNAME$", "message": "$NOTIFICATIONTYPE$ - $HOSTNAME$ is $HOSTSTATE$", "ip_address": "$HOSTADDRESS$", "severity": "$HOSTSTATE$", "event_id": "$HOSTEVENTID$", "output": "$HOSTOUTPUT$", "perf_data": "$HOSTPERFDATA$", "action_url": "$HOSTACTIONURL$", "check_command": "$HOSTCHECKCOMMAND$", "problem_id": "$HOSTPROBLEMID$" , "long_datetime": "$LONGDATETIME$", "notification_comment": "$NOTIFICATIONCOMMENT$", "notification_type": "$NOTIFICATIONTYPE$", "contact_name": "$CONTACTNAME$", "last_problem_id": "$LASTHOSTPROBLEMID$" }" /api/notify/nagios

Tickets can be created in Halo whenever an Alert is triggered in Nagios.
To enable this functionality, create outgoing webhooks in Nagios for the Host-Alert, Service-Alert events.

logisbk wrote: ↑Thu Apr 02, 2026 12:28 pm We have certain subset of hosts/service in our environment that we would like to generate tickets when there is an issue. These hosts are assigned a specific contact. I have created two event handlers (host event handler and service event handler) that will create tickets, and under the contact Alert Settings tab, select Manage Host/Service Notification Commands > select the respective Command/Event Handler. This is working correctly if the contact is assigned directly to a Host or Service. What I found that doesn't appear to work, is if the Contact if inherited it will not use the event handler (host/service notification command) as defined in the contact.

For example, Host A has the contact directly assigned and works as expected. There are two Services associated, Service 1 and Service 2. Service 1 has the contact directly assigned and works as expected. Service 2 has no contacts or contact groups directly assigned, so I would expect the behavior to be that it inherits the contact from the host, and thus will use the event handler. Service 2 does not generate tickets as expected.

Anything I am missing or explanation for this not working?wheelie life