Learn everything you need to know to migrate you and your team to Atlassian accounts.
Launch your status page
We put together this guide to help you launch your status page quickly. Getting a basic status page up and running doesn’t require an engineering team or any heavy lifting, in fact, most customers set up their page in less than 30 mins. Just follow these 6 steps for success!
Step 1: Create your components
Components are the individual parts of your infrastructure that your users depend on, or the functioning pieces or features of your application/service (your website, API, mobile app, etc). They help you tell your customers which parts of your product are affected by an incident.
If you haven’t already, go ahead and add some components to your page. You can always add or remove them later.
Tip: We recommend using component names that are clear, concise, and easy to understand, but sometimes additional context is helpful. Add descriptions to your components to give your users additional information.
Step 2: Brand your page
Before you go live with your status page, take a few minutes to make sure you’ve introduced your company’s brand on your page. Here are some quick wins:
Add a page logo or a custom header image
Add an email logo (if you’re using email notifications)
Add a page favicon
Add a Twitter card image (if you’re using the Twitter integration)
Change the page colors to match your brand
Set up a custom domain
Step 3: Clean up any test or example incidents
You might have created a couple test incidents as you were evaluating Statuspage. Head over to the Incidents page and delete those before you launch your status page. You don’t want to confuse your customers with incidents that never occurred!
Step 4: Prepare your team & create an incident response plan
This is a really important one! A status page isn’t very useful without a team responsible for managing it and a plan in place for how to use it. Some things to consider:
Define who owns the status page.
Make sure the necessary team members have access to manage the page.
Create an incident response plan so you know when and how to use the status page.
Create incident templates so you can communicate quickly and consistently
Step 5: Subscribe your customers to your page
Statuspage helps you keep your customers in the loop by optionally sending them email and text message notifications when you publish incidents on your status page. You can create one-off subscribers using the manage portal, or you can leave it up to your customers to subscribe to notifications on their own. You can also bulk create subscribers using the API or uploading a .csv file.
Step 6: Announce your status page and continue to increase awareness of it
Once your page is live, you need to let your users know it exists. A status page is an incredibly valuable tool to end users, and there are several ways you can make sure they know about it. Here are some ideas:
Send your customers an email announcement with a call-to-action to subscribe to your status page
Embed your system status into your application UI, website footer, and help center
Use the Twitter integration so that your followers are automatically updated when you post an incident
Bonus: Integrate monitoring and alerting apps
You might be looking to automate your status page. There are several ways you can do that using monitoring and alerting tools like Opsgenie, Pingdom, New Relic, PagerDuty, and more.
Note: as a best practice, we don’t recommend fully automating your status page.
Was this helpful?