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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,463,038
Community Members
 
Community Events
176
Community Groups

Mapping alert values from Solarwinds

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?

1 answer

1 accepted

1 vote
Answer accepted
Nick H Atlassian Team Mar 20, 2020

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:

priority 1.jpgpriority 2.jpgpriority 3.jpg

 

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.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events