Re: Contact Host and Service Event Handler/Notification Commands
Posted: Mon Apr 13, 2026 2:34 pm
Maybe a little bit of both...logisbk wrote: ↑Mon Apr 13, 2026 12:44 pm What I've noticed is that an alert may create multiple tickets and not update the ticket, and then it may close only one of the tickets. Also, I was looking into an issue when in the Service Notifications for a service it said it sent an notification to the contact using the custom dispatcher (the custom notification command), but I couldn't find a ticket in Halo at all. This may not be a Nagios issue but @-SN if you have insight for Halo specifically let me know
With "most" upstream ITSM applications you'll have a method that can be utilized for deduplication, the problem is that you're already at the incident level which doesn't leave you any room for aggregation/escalation. To help fill this gap I use a combination of Nagios macros and object custom variables to help provide context for upstream processing.
If I remember correctly Halo has the ability to merge duplicates with both the UI and API but, that's all up to the end user scripting ability. You can however create custom fields and use that with your workflows.
Nagios provides two unique auto-incrementing fields for each type of monitoring object.
{X}PROBLEMID and {X}EVENTID
I use these two fields to create the dedupe key.
- Host Deduplication Key = $HOSTADDRESS$-$HOSTPROBLEMID$
- Service Deduplication Key = $HOSTADDRESS$-$SERVICEDESC$-$SERVICEPROBLEMID$
- Host Resolve Dedupe = $HOSTADDRESS$-$LASTHOSTPROBLEMID$
- Service Resolve Dedupe = $HOSTADDRESS$-$SERVICEDESC$-$LASTSERVICEPROBLEMID$
In Halo you'll also have to play with the "tickettype_id" I can't for the life of me find the notes for all the types but, should be available through help in the UI. You can use the rest of the notification macros to help with some of the inner workings of Halo once you get your footing.
Happy Monitoring!
--SN