You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
We have setup in a test cloud the opsgenie integration with dynatrace.
We have use for that Dynatrace Webhook
Once the dynatrace integration has been done, we have configured it to accept all alert first in order to see that all are coming in opsgenie.
We notice 2 scenarios :
Case 1 : Alias default mapping to Dynatrace PID
=> with this maping opgenie is actually creating an Alert on Dynatrace OPEN and RESOLVED problem ( so one alert for each status)
This is not what we want of course, so we change teh Alias mapping to match scenario 2
Case 2 : Alias default mapp to Dynatrace ProblemID
=> alert is created in opgenie on dynatrace OPEN status problem
=> alert is updated ( last update field change) in opgenie on dynatrace RESOLVED status problem BUT the alert is not closed by opsgenie
Any idea what could be wrong ?
Problem solved it was a mismatch mapping field