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,821
Community Members
 
Community Events
176
Community Groups

2 alerts are created automatically when creating an Incident

Hi.

Does anybody know if it's possible to avoid new automatic alert creation when an incident is created from an alert. Is mandatory to get 2 new alerts or are we missing something? Seems to be quite redundant

The process is as follows:

  1. An email is sent to the account we have setup to receive alerts
  2. The alert is automatically created and communicated to the team
  3. Someone in the team "acknowledged" the alert
  4. The user/operator creates an incident from the alert
  5. 2 new alerts are automatically created with the incident information

Thks!

1 answer

0 votes
Nick H Atlassian Team Jul 20, 2022

Hi @Pedro Parellada ,

That's the current workflow with Opsgenie incidents.

Say for example an incident is created automatically through an incident rule, and the incident rule is tied to a service:

inc1.jpg

 

The service adds multiple responders to the incident at creation:inc2.jpg

 

The alert that initially created the incident would become an Associated alert - and doesn't notify anyone.

The incident then creates a Responder alert for each responder added by the service, and does notify each responder:inc3.jpg

 

The idea behind this workflow is that each responder might have a different configuration in which they need to be notified when an incident triggers; each team could have different routing rules or escalations that manage incidents vs. alerts, each user might have different notifications rules for incidents vs. alerts, etc.

Hope that helps make sense of why two (or more) alerts are created for an incident. And unfortunately at this time there isn't a way to disable this workflow.

Thks for your answer Nick. Regards!

Like Nick H likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS

Atlassian Community Events