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,551,769
Community Members
 
Community Events
184
Community Groups

Alerts routing within a team

Hi,

I'm setting up multiple teams in Opsgenie (DevTeam1, DevTeam2, ...). Within a single team, they might have different slack integration to be able to send specific alerts to different Slack channels.

How can I setup my integration so that if an alert matches the condition for a channel it is not send to any other integrations?

1 comment

Nick H
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jul 07, 2021

Hi @Benjamin Souty ,

Unfortunately that's not possible. The Slack integration does not have functionality to know if an alert has already been sent to another channel. As long as an alert matches a Slack integration's filter/defined conditions, it will send messages to that configured channel.

There really isn't much of a workaround either. You could differentiate each Slack integration's filter from the others, but I'm sure that doesn't meet your use case.

Like Benjamin Souty likes this

I was hoping to avoid that but that's good to know.

The plan was to use labels on kubernetes resources to route alerts to a specific team and then if needed to a specific Slack channel.

On the other hand, routing to an additional dedicated channel shouldn't be something we often do and when we do, it's usually temporary. So setting a rule on a dedicated integration and the catch all one won't be a big deal. Just would have been nice :)

Thanks for your answer.

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events