Opsgenie - CheckMK integration with multiple teams doesn't create multiple alert

Dipayan Sil

Dears,

I have an Opsgenie setup with 2 teams. Both the teams have integration with same Checkmk instance. Integration for 2 teams in Opsgenie is configured with 2 different users in Checkmk with corresponding API key. However when the alerts are created, it is only visible / created for 1 team. 2nd team do not get the alert created and hence no notification is generated for on-call person of the 2nd team. Is there anyway that Ops genie can create 2 alerts to 2 different team for 1 alert from Checkmk?

 

Thanks.

Aysun Özgün

Hey @Dipayan Sil,

I'm not entirely sure if CheckMK is capable of triggering two different Opsgenie integration endpoints for the same host or service problem. However, with your explanation of your setup; looks like this is possible. Only one alert is getting created instead of 2 separate ones might be due to deduplication.

When the received data contains the same alias value of an open alert; that data deduplicates the open alert instead of creating a new one. When an alert gets deduplicated, its count increases. Overall, alert de-duplication is a feature presented for reducing alert and notification fatigue; with not sending notifications over and over again for the same alerts. For further information you can check this doc: https://docs.opsgenie.com/docs/alert-deduplication

This being said, if you're looking for avoiding deduplication; you can customize the alias value upon alert creation. This can be done through Advanced settings of CheckMK integration on Standard and Enterprise plans. Let me also share the related doc here: https://docs.opsgenie.com/docs/advanced-integration-settings

On CheckMK integration; by default, "Host Name" is designated as alias for host alerts. For Service alerts; it is designated as a combination of "Host Name" and "Service Description".

Instead of "{{hostName}}_{{serviceDesc}}"; you can you can update the alias field such as with "TeamA_{{hostName}}_{{serviceDesc}}" for one integration so that the second data would create a new alert instead of deduplicating the open one.

Please note that; if you update the alias field of Create Alert rules, you might also need to reflect this change to Close Alert and Acknowledge Alert rules since alias value is also used to find the matching alert to apply Close and Acknowledge action to the data sent from CheckMK.

Hope this answers your question!

In case you need further assistance with checking the logs for deduplication or setting up alias field; you can reach out to Opsgenie Technical Support Team through in-app chat or from https://support.atlassian.com/opsgenie/