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

Should an incident impacting a service also impact dependencies?


I've been wondering how the service relationships work.

My situation represented by a simplified example:

  • There are 2 services defined, P and Q
  • P contains Q
  • There is a rule for an alert that triggers an incident on P
  • This only changes the state of the service P

Should this change the state of Q, or this has to be manually (or via API) done? Is there any best practice for this?

1 answer

0 votes

Right now, the service relationships are just for display and reporting purposes. There isn't currently a way to trigger an incident on a dependent service if the 'parent' service has an incident.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events