Compass Components and JSM "Operations" Services in "new" JSM

[Ken Young]

Hi All,

I am wondering if there is any changes (current or upcoming) in how Compass Components and JSM (Operations/Affected) Services interact with OpsGenie being folded into JSM.   We haven't been upgraded because we are currently using JSM/OpsGenie, but I am wonder if there have been any changes that would effect their use, and possibly Automation opportunities.  Thx

[Katie Silver · Accepted solution]

Hey @Ken Young , we're working out the details of this now. When we are closer to releasing the on call and alerting functionality in Compass, I'll make sure to update here. 

[Ken Young]

Thanks @Katie Silver .  I think I misread a different document and though a new feature had rolled out..   I thought I read if a "App Service" component was created in JSM, a Component was automatically created in Compass--- possibly thinking there had been a change with how the GitHub integration will now dynamically create a component when a new GitHub repo is created.

Thx

[Abhinaya Sinha]

Hi @Ken Young - as I mentioned in your other query, we are releasing alert and on-call capability in Compass. We are currently in early access program but starting the rollout from now until early November. So you can expect to see this soon.

[Michael Wright]

Hi @Abhinaya Sinha  thanks for your response and update on this.

I just wondered if there are any prerequisites for oncall and alert capapbility being rolled out to compass instances where organisations are in the 'moving to Opsgenie' process. We are currently part way through this and wondered if the roll out would be dependent on Opsgenie being in 'read only' mode or turned off? Or if there are teams within JSM Ops will these new features be rolled out regardless of where people are within this process?