When will the OpsGenie feature that allows monitoring of 3rd party Atlassian Status Pages be migrated to JSM?
This doesn't appear to be covered in any of the migration documentation or FAQs shared since the merge was first announced over a year ago.
A large number of the SaaS and IaaS providers we rely on are enterprise customers of Atlassian using Atlassian Status Pages to update their customers.
Loosing the ability to subscribe to these pages seamlessly within the Atlassian ecosystem is far from ideal.
This lack of feature parity between OpsGenie and JSM is one of the reasons I paused our migration mid last year.
For anyone unfamiliar, this feature can be found in OpsGenie here and allows you to start typing the organizations fully whitelabelled or atlassian subdomain StatusPage:
The similar service monitoring configuration in JSM offers no ability to target a providers Atlassian Status Page:
Status Page monitors that were created in OpsGenie are now configured in JSM as a 'Software Service' type that targets a Service ID which appears as a very long random chain of characters. This long random chain of characters is no available if accessing an organizations Atlassian StatusPage directly. Its some kind of internal reference.
Further more, that Service ID field is an unconfigurable and read-only field that only appears after a you've created a new service via JSM. From what I can gather it is currently impossible via any means to create a similar monitor directly in JSM.
An example of what the Service ID's look like (this is not a real service ID):
b:YXJpOmNsb3VkOmdyYKBoOjpzZXJ2aaNlLzRmODZYjkyLWNkYmQtNDY1ZC1hZDq5LTgzNzEyMTliZWU3Ni8yMzRkZTQ0Mi0zOTY3LTExZWUtODI4Yi0wYWJlx2Y0YTY2MDE=
@Darius Great question!
We will update the document as well to have this information.
Any external services configured will be moved to JSM and Compass, however creating new external services will not be supported.
For you existing external services, you will continue to get alerts from statuspages subscribed to.