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

Using LibreNMS severity levels to set priority levels in Opsgenie

Hi there I am wanting to create different priority levels for LibreNMS alerts based on the severity levels sent by Libre.

Potentially making it look like this:

  • P1 - Critical
  • P2 - Warning
  • P3 - OK

I am presuming it can be done with the Custom Priority section of the integration, but I'm not quite sure on how to do it as I have only been able to get it to assign a single priority level no matter the severity level.


1 answer

1 accepted

1 vote
Answer accepted
Nick H
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Sep 20, 2021

Hi @Josh Hodkinson ,

This can be configured under the Advanced tab of the LibreNMS integration. Note that this tab is only available on the Standard and Enterprise plans.



By configuring multiple Create Actions, each can filter on the Severity being parsed in the payload, and map to the corresponding Opsgenie alert priority:



Like you mentioned with the Custom Priority section of the integration, you can also use this to extract the numerical value (if being sent in the payload), and use one action to also map to the corresponding priority dynamically. It would depend on how / where the numerical value is being parsed, but typically we see something like this string process method work well:



Hope this helps! Let us know if you have any other questions.

Looks like we're upgrading then.

Thanks for the help will be using it once we do upgrade our plan.

Like Nick H likes this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events