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

opsgenie and alertmanager integration yaml file

Hi everyone,

I am trying to get alertmanager to forward alerts to opsgenie.

I have had a look at - but reading that page didn't help much.


I found the following thread on this forum:

but then again when I run that code, I get the following error in the alertmanager container:
err="yaml: unmarshal errors:\n line 10: field priority not found in type config.plain"

Below is my alertmanager.yml file:

  resolve_timeout: 1m
  opsgenie_api_url: 'XXXXXXX'
  opsgenie_api_key: 'XXXXXXX'
  - opsgenie_configs:
    - responders:
        - type: team
          name: "TwigOps"
    priority: '{{ range .Alerts }}{{ if eq .Labels.severity "critical"}}P1{{else if eq .Labels.severity "warning"}}P2{{else if eq .Labels.severity "info"}}P3{{else}}P4{{end}}{{end}}'
    name: opsgenie
  group_by: ['alertname','service']
  receiver: opsgenie
  repeat_interval: 5m


Is there a template file I could download? It seems to me that the above code might be missing some declarations which is why "priority" is not found as a field.


Thanks for your help

1 answer

0 votes
Samir Atlassian Team Jan 31, 2022

Hi @Guillaume Bettayeb ,


Have you tried it with setting priority as just a value of "P1", "P2", etc.?

I am wondering whether the conditional statements you are using for the priority field is are whats causing the issue.


If you could change it to just a hardcoded priority value of P1, P2, P3, P4, or P5, that would help rule out what's causing the issue with the priority field.




Suggest an answer

Log in or Sign up to answer

Atlassian Community Events