Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


OpsGenie-Grafana integration issues for a setup with multiple Grafana instances and OG integrations


We've had some issues with alerts from Grafana integrations going missing in OpsGenie due to unintended alert de-duplication. There are issues with the OpsGenie-Grafana integration for a setup with multiple Grafana instances and/or multiple OpsGenie-Grafana integrations. Is this a known issue at OpsGenie?

See posted issue at the Grafana repo for more details:


Nick H
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Feb 17, 2021

Hi @Gustav Janér ,

I don't think it's an issue. Deduplication occurs when alerts match the alias of an open existing Opsgenie alert - regardless of what integration they come from.

It seems like your Grafana instance is configured to multiple Opsgenie-Grafana integrations. And when requests are sent from Grafana to Opsgenie, only one alert is created due to the alias matching.

You can adjust what data parses as the alias in each integration's Advanced tab:



You'll notice there are dynamic fields that can be dragged and dropped on the right. But in your case, it might be easier to use something hardcoded for each integration. This would help avoid deduplication.

Here's a simple example of how that can be applied to two integrations:



If you do edit what parses in the alias - through dynamic fields or hardcoded data - you'll want each action of the integration to also use the same. This ensures consistency, and Opsgenie will know which alert to close, ack, etc. through the integration:



Hope this helps! Let us know if you have additional questions or issues.

Like Gustav Janér likes this

Thanks for your answer! I'll try that out!:)

Thanks for this solution but there is still a problem about different alerts triggering from the same grafana. only one ticket is opened in Opsgenie and rest of the alerts of same alias didn't count as separated alerts. The only evidence for them is in the activity log of the first alert opened in OG.
Is there any workaround for this?


Log in or Sign up to comment
AUG Leaders

Atlassian Community Events