We're currently implementing JSM and using Assets & Services.
For our CI, we've taken the Services route rather than creating a technical services schema with objects to leverage service reporting, MIM & change enablement.
This approach leaves a bit of a gap in our needs.
I've read a few posts about upcoming Opsgenie & JSM integration. I'm keen to learn more about this roadmap. Specifically:
We're a bit of a hybrid team, so I'm looking to eat the cake too :)
Also, if you can add here, I'd love to get a bit more details on what you mean by "This approach leaves a bit of a gap in our needs."
What are you trying to achieve? What have you setup today and what is breaking down?
Thanks, Taylor. I'm keen for a catch-up; let me see if one of our architects is eager to jump into this too. It's new exciting territory for the team.
We have set up Asset with a business services schema containing our business services in the end-user context. We then have Object Types to represent the systems, classifications etc., and then we pull in our technical services from Opsgenie.
From an architecture and engineering perspective, we think Compass can help us with team-level management, dashboards, doccos, feature flags, APIs, libraries etc.
The gap will be bringing this all together for Global IT Operations. Some of these services will transition to support; some will not. We want to ensure both sides of the fence have visibility and transparency over our ecosystem.