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

How do you decide on what components to show on your status page?

We're trying to identify what components to show on the Status page and we're seem to be stuck on identifying what make sense. Im hoping to hear best practices or how you decide on what to show on your page.

2 answers

2 accepted

1 vote
Answer accepted

Hey @Michelle Bautista , welcome to the Atlassian Community!

I'm from Broadcom, a long-term Statuspage customer! I just wanted to draw on what @Jake Bartlett has provided and give you an example on how we decide what components we share across our 13+ pages.

As most of our products are Saas/Cloud and vary in how they are configured, we have two types of structure we typically follow:

  • Customers provisioned in regions or data center's, so our structure is to have the Product name as a group/parent component and then underneath we have the regions (example: our Symantec Email Security page shows our .cloud product split into regions)
  • Customer-facing components that make up the platform of that product for example our Cloud Workload Assurance product has a customer facing portal and a provisioning API that our customers use so we structured our components.

I always recommend thinking about your products/platform and what issues your customers may face then structure the components on what customers will know. Always make sure your components make sense to your customers.

You can check out our Statuspages here which hopefully gives you some ideas.

Cheers,
Nick Coates
Product Owner - Service Status, Broadcom Inc.

1 vote
Answer accepted

Hi @Michelle Bautista thanks for the question! The best way to determine what components to include on your status page is to consider what important services, features, or products your customers depend on. What items / services have had outages or performance issues in the past? What are the most important parts of your service to your customers?

For example, you might have a mobile app, a website, a help center, and an API -- all of those could be components. You could even drill in further and add individual features as components (e.g. email sending, notifications, file uploads). Here are a couple links with additional information:

We recommend keeping components to a manageable number. Start small and add more as needed. You can also use component groups to keep things organized. 

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events