You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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.
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:
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.
Product Owner - Service Status, Broadcom Inc.
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.