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
Next: Root
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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I'm using the Solarwinds integration, but alerts are defaulting to P3 since severity in solarwinds does not match priority in Opsgenie. The Mapped priority Value documentation is a little vague. I want to map Sev Critical to P1, Sev Serious to P2, Sev Warning to P3. How do I set this?
Hi Scott,
Like you mentioned, Solarwind severities typically do not match to Opsgenie priorities out-of-the-box. So we see most customers mapping Severity -> Priority on the integration level.
Under the Advanced section of the integration, you can filter on the data being sent from SW (such as the severity) and map to the corresponding priority:
In my screenshots I built out your 3 severities (Critical = P1, Serious = P2, and Warning = P3).
It's important to note most of Opsgenie follows an order of operations -> meaning Opsgenie will try matching to the top action/filter and if no conditions are met, look at the following action/filter(s), etc.
Let us know if you have any additional questions or concerns about this configuration!
That's exactly what I ended up doing. I was hoping to keep it down to one profile with mapping, but couldn't figure it out. Thanks for your post. I'm sure I won't be the first one to have this question.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.