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!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Alert deduplication and alert status updates

Hello Atlassian Community,

We are looking into opsgenie to handle our alerts from multiple systems (mainly Azure) and have a question about alert deduplication.

When an alert is deduplicated, it increments the counter, which is really convenient to lower alert spam, but we are losing the additional information which that alert would send. Extra alerts usually mean that something has changed, and we don't want to lose that information.

How would we go about in catching that information?

We are currently adding certain fields as notes in the create to provide status updates, but maybe there are more convenient solutions (or maybe this should be a feature request as a possible optimization for opsgenie)

Any ideas?


2 answers

1 accepted

1 vote
Answer accepted
Nick H Atlassian Team Mar 29, 2021

Hi @Kevin De Wolf ,

Like you are currently doing, the best method is having a Note added each time the alert deduplicates, and include the additional data/fields through this approach.

Alert fields cannot be updated when an alert deduplicates. We do have an open feature request I'll add you to though! That ticket for reference is ALX-918; Update alert fields / content upon deduplication.

Since our tickets are not public, we'll reach out directly if/when there are any updates. Let us know if you have any other questions, issues, etc.

Hello @Nick H 

Thanks for the quick and clear answer.

Good to know that we're on the right track, and I'm looking forward to hearing from ALX-918, as I'm sure this would add alot of added value.

Hello @Nick H 

I think this will also solve my problem detailed  here 

Like Nick H likes this

I ran into this exact situation doing a three way integration.

My solution was to write a python AWS Lambda that intercepts alerts from our secondary source that's guaranteed to send alerts on a time delay (so these are deduped).

Then point the corresponding integration to the API Gateway URL to invoke said lambda, instead of the official OpsGenie endpoint.

The lambda's logic simply takes the details{} payload and uses Alert Details Update API to insert the same payload into an existing alert. Auth headers are forwarded from original headers.

It takes a bit more logic if the lambda is for all alerts instead of having a source which is guaranteed to come later.

Since you're in Azure, perhaps Azure Functions does the same

Suggest an answer

Log in or Sign up to answer
Site Admin

Atlassian Community Events