Hey @Oliver Wemyss and @Will Le, thanks for bringing this up!
I would love to dive into the details of the Application Governance program you want to set up in Compass in order to better understand how our current priorities align and whether we can change those to better support your use case.
If you can spare 30 mins grab anytime here: https://calendly.com/tpechacek/compass-alpha
To your question: Yes, there will be a relationship with JSM Services, Opsgenie Services, and Compass Services. We are working with those teams to continue to evolve our offerings around a service object and make that as seamless as possible so you have that dependency chain.
However, Compass is currently still hyper-focused on the developer experience within software organizations that has a "You Build it, You Run it" DevOps mentality. (i.e. a single software team is responsible for building and operating different software components - mainly microservices or common libraries).
Many of our Alpha customers are not currently using Insight or any form of a CMDB, but almost all of them are using some combination of Jira Software, Bitbucket or GitHub, a CI/CD tool, and some observability tools like New Relic, Datadog, Splunk, or Prometheus.
So, the question becomes when and how do we wire up JSM (inc. Insights) and Osgenie. Let me dive into our current thinking here.
- We are currently working on a Jira integration to map the components field on issues to the components in Compass. This works across JSW and JSM because it's a core field across all of Jira. This should be out very soon, it's on our staging environment.
- For Jira Service Management, they have already done some excellent work connecting the 'services' on the JSM project with the 'service' object in Insight as well as Opsgenie. JSM also has an 'affected services' field that is different from the component field used in JSW, so we will need to connect with them.
- Compass will look to sync the component types of 'services' to the services that are represented in JSM, Insight, OG and vice versa so that you have 1 single, consistent representation of the Service object but built around different use cases.
In the meantime, you can import components in bulk through the GraphQL API or a CSV importer tool we built. This is a one-time import though so the information is likely to drift over time.
If you do need to unblock yourself, you could invest in a Forge App (or your own small microservice) that takes the data you have in Insight and then updates the information in Compass. The APIs are all publicly available to do this. Let me know if you would like some help mapping that out. Otherwise, if you can wait a few months we will likely get to this by then.
Is there anything else you would expect / like to see that is not captured above?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.