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!


Opsgenie Services best practice?

I am looking to setup Opsgenie services and have a general question. If an organization has multiple Products, call them A, B, and C. If each of these products is comprised of many engineering components, like APIs, DBs, etc, do you setup the Services to be just A, B, and C or do you build them out to all of the components that make them up? 

1 answer

1 accepted

0 votes
Answer accepted

Hi @Evan Giordanella, I think there is no correct answer for your question. For example, if a failure of a Product's component affects the full functionality of the Product, I would associate the component to the Product's Service. If not, I would create a Service for the component itself.

Product X:
  * API: If the API fails, then it affects *all* Product X. 
  * DB: If the DB fails, then it affects *all* Product X. 
  * UI: If the UI fails, Product X is able to function and only affects the UI. I would create a Product X - UI Service.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events