Atlassian’s new System Health feature is now in open beta!

[#1]

Hi admins! I’m Ed, a Principal Product Manager here at Atlassian building new features to help you monitor and optimize the reliability, scalability, and performance of your Atlassian apps.

We know that Atlassian apps are mission critical to your work, and we take our responsibility to keep them running smoothly seriously. We also know that when an incident does occur, you need transparent information to keep your teams in the loop.

Today, I’m excited to announce a major step forward in that transparency. System Health is now rolling out in open beta to all cloud customers! You are automatically enrolled and it will appear in Atlassian Administration over the next month.

What is System Health?

System Health is a new reliability monitoring and incident communication feature in Atlassian Administration. It helps you stay aware of incidents by using personalized dashboards and alerts to surface incidents that are only relevant to your sites and apps. With System Health, you can:

• Monitor the operational status of your Atlassian apps

  • Operational: No incident has been detected.

  • Advisory: An incident has been detected, but site impact is not confirmed.

  • Confirmed impact: An incident has been detected and is confirmed to be affecting one or more of your sites.

• View site-level incident and resolution data

• Access a 90-day incident history

• Receive automated alerts for Jira, Confluence, Jira Service Management, and Bitbucket
  

How does it differ from status.atlassian.com?

We’ve heard you loud and clear: incident reporting should be simple, transparent, and tailored to your specific organization. While status.atlassian.com is a public resource that reports broad incidents and the global operational status of Atlassian apps, System Health tailors this information to your specific organization. It provides site-specific monitoring and targeted alerts for incidents that directly affect your apps, as opposed to the global Atlassian Cloud.

How does it help you?

• Reduce noise and save time by seeing only incidents that affect your sites and apps, so you don’t have to sift through irrelevant updates.

• Keep your teams informed of incidents faster with personalized dashboards and instant updates on incident scope, affected apps and sites, and resolution progress.

• Monitor apps with less effort thanks to automated email notifications for critical incidents in Jira, Confluence, Jira Service Management, and Bitbucket.

• Report historical reliability with confidence using incident logs to deliver consistent insights to stakeholders and leadership.
  
  

Who can participate in the open beta?

All org admins on any cloud plan. All eligible organizations are automatically enrolled in the Open Beta, so there’s nothing to set up. Org rollouts started on November 10th and will be completed in December, so you can start using System Health as soon as it’s available in Administration!

How do you access System Health?

1. Go to admin.atlassian.com

2. Select your organization

3. Navigate to Insights → System Health

4. View the status of your apps and see if there are any active incidents

5. (Optional) To receive automated email notifications, open Notification Settings in the top right corner and toggle on Send me emails about incidents

What’s next?

As we move toward general availability, we’ll continue making improvements based on your feedback, which you can provide in the comments or by using the Give Feedback button located in the top right of the System Health experience.

We’re excited to partner with you to make System Health even better through the beta period, and will share more updates as we progress.

Thanks,
Ed

[Tim Eddelbüttel]

It's definitely an improvement but it's "hidden" behind administration. 

Looking what others are doing. In this case Zendesk. I've had a situation where the Zendesk Jira integration stopped working. I'll head up to the https://status.zendesk.com. Globally everything was fine. I'll discovered that you can enter the site / tenant / subdomain (e.g. shopify, squarespace, etc.) and see the corresponding status for the site which can be different. With that information i could simply remove Jira as a root cause. 

Having these similar for Atlassian Cloud would be great.

[__ Jimi Wikman]

This is great!

[Ed Huddart]

Hi @Tim Eddelbüttel - thanks for the feedback!

We're planning to make System Health accessible to more users outside of org admins in future - so please stay tuned as we continue to expand its functionality.

That said, in order to protect customers' privacy, we'll only ever provide information about an organization to people who have been explicitly designated to receive it by their admins. For that reason our solution probably won't ever look quite like Zendesk' - but eventually will serve almost all of the same use cases.

[Tim Eddelbüttel]

@Ed Huddart i wouldn't agree that entering a site title puts any privacy at risk. If XYZ is a customer is already possible today (e.g. just entering the page, check availability while register a new site, etc.).

[Alfonso Leiva]

Am I the only one not seeing the System Health option?

[Ed Huddart]

Hi @Alfonso Leiva - we roll out most new features like this gradually, with an incremental percentage of customers getting enrolled each few days. If you don't see it available on your org now, you should see it by mid December at latest!

[Clairee Daniels]

@Ed Huddart 

I have a few questions regarding this feature:

1. Integration with Statuspage: Can we hook this into our internal Statuspage? Specifically, if Atlassian experiences an incident, would it be possible for our internal Statuspage to update automatically? Additionally, is there an option to trigger the creation of an internal Operations and/or Jira Service Management incident when this happens?

2. Notification Recipients: If we enable notifications, who will receive them? Will it be sent to all Org Admins, or can we designate specific users to receive these alerts?

3. Customer Tier: Is this feature available only for Enterprise-level customers, or can Premium customers access it as well?

Thank you!

[Ed Huddart]

Hi @Clairee Daniels - great questions!

1. Integration with Statuspage: Can we hook this into our internal Statuspage? Specifically, if Atlassian experiences an incident, would it be possible for our internal Statuspage to update automatically? Additionally, is there an option to trigger the creation of an internal Operations and/or Jira Service Management incident when this happens?

This is not currently possible in the beta version, but we plan to support this use case in a future release via automation & an API endpoint.

2. Notification Recipients: If we enable notifications, who will receive them? Will it be sent to all Org Admins, or can we designate specific users to receive these alerts?

Only the org admin(s) who click the opt-in toggle with receive notifications. So if you want all org admins to receive them, then each individual must click the opt-in toggle themselves.

In a future release, we will add the ability for org admins to designate other users (such as site admins) to receive notifications as well.

3. Customer Tier: Is this feature available only for Enterprise-level customers, or can Premium customers access it as well?

Once rollout is complete, System Health will be available to all customers regardless of their plan.