Value Stream Management (VSM) relies on automation. No developer wants to document things manually, especially not in a continuous delivery world. We support our customers in two ways:
- With out-of-the-box integrations, you can get started extracting your data within minutes. It could be a plugin, or it could be a scheduled job hosted by us.
- With powerful APIs that enable you to build your integrations and leverage our platform capabilities to monitor them & keep them up-to-date.
VSM combines information from typical phases of your software development lifecycle. The goal is to support your development team with intuitive, up-to-date documentation - so work with them to understand what to extract and how.
- Development time - Some information like team ownership or used programming language can be pulled directly from source code repositories
- Deployment time - pushes out of your CI/CD pipeline give an easy insight into what's deployed and when. Typically they are the easiest starting point for your documentation but need to be augmented with more information to capture all aspect
- Runtime - in addition to deployment time, runtime information (e.g., from Kubernetes) helps you to validate what should be live (deployment) against what is really live - helping to identify & address the so-called Architecture Drift
- Finally, information from [supporting systems (like API management, vulnerability scanners, ...) can augment development, deployment & runtime information to obtain the full picture.
Always get information from where it logically belongs, e.g. deployment time information shouldn't come from a runtime environment like Kubernetes but directly out of your CI/CD pipeline.
OOTB vs Community Driven
Out-of-the-box integrations are fully developed and supported by LeanIX.
Community driven setups are contributions of our best-efforts from & to the community. As such, regular LeanIX service SLA and support do not apply to these projects. We are open to discuss the work and are of course open to any contributions by the community 💙
|Tools||Key benefit||Out-of-the-Box Integration||Community Driven Setups|
|The LeanIX VSM GitHub Repository integration offers an easy way to auto-discover all your services from GitHub organization(s), populating your VSM workspace at scale.||GitHub||VSM SBOM Booster|
|The LeanIX VSM GitLab SBOM Booster offers an easy way to auto-generate SBOMs for a lot of your services, boosting your journey to get full SBOM coverage.||Planned||VSM SBOM Booster|
|The LeanIX VSM Azure Repository integration offers an easy way to auto-discover all your services from Azure Repos, forming a strong baseline to populate your VSM environment at scale.||Azure Repos|
|The LeanIX VSM Bitbucket integration offers an easy way to auto-discover all your services from Bitbucket SaaS setups, forming a strong baseline to populate your VSM environment at scale.||Bitbucket||VSM SBOM Booster|
|The Kubernetes (k8s) Integration helps you understand which version of your services runs on which cluster. It shows how the software package built in your CI/CD pipeline is deployed on your Kubernetes clusters.||Kubernetes|
|The integration with LeanIX EAM allows you to map the products you develop into the wider architectural context of your organization - how they relate to business capabilities, processes, and more. On the inverse, it automates technical information, such as open-source risk, to the reports your Enterprise Architects already use today.||Enterprise Architecture Management|
|This integration discovers the services created in your PagerDuty instance and creates the necessary incident events. Mapped to your service catalog, VSM will use this data to compute the Change Failure Rate (CFR) and Mean time to recovery (MTTR) DORA Metrics for your teams and services automatically.||PagerDuty|
Your favourite integration is missing?
Check our roadmap and submit your ideas.
VSM offers state-of-the-art APIs to use REST or GraphQL to execute most actions programmatically (e.g., import data).
The REST-based Discovery API can be used to bring Team, Service, SBOM, and Product data into the VSM catalogs, including specific meta information such as descriptions, tags, and relations. Through this, it is possible to bring in information from further sources that no OOTB integration can discover, for example, by pushing data as part of your CI/CD pipeline builds. Technical information on the API can be found here, and a few example tutorials are below.
The REST-based Events API complements the above with the possibility of bringing release, incident, and change events into VSM. This can, in turn, be processed as DORA metrics on your services and teams, expanding the out-of-the-box functionality provided by the repository and PagerDuty integrations. Technical API documentation can be found here.
The GraphQL API gives you access to the VSM knowledge graph, i.e., all the information about teams, persons, services, libraries, products, and their relations. This essentially allows you to do anything programmatically that you might otherwise do via UI.
To access the GraphQL API, please use the GraphiQL Explorer available right in the VSM Workspace under Administration> Developer Tools. There, you can run queries and mutations of the data stored in VSM.
The stages can be summarized as follows:
|Expectations||Not Available||Early Access||General Availability|
|Customer Availability||None||Integrations are invite only or must be enabled by your Customer Success Manager or Sales Engineer.||Available to all users|
|Support||No||Yes, but no SLAs||Yes, with full SLA|
Although this is not a de-facto release status, any integration not found on VSM documentation or roadmap is currently not planned for. Hence, there is also no committed timeline. If you believe you’re missing an integration, we are more than happy to hear from you via a Zendesk ticket or [email protected].
This integration is under development and supports VSM in collecting early feedback and issues by early adopters. Integrations in this stage should be experimental and by no means production-ready. APIs in this stage might change unannounced. At this stage, there is no binding support SLA.
Aspects to note:
- integrations in this stage are feature-complete but can still contain breaking (API) changes
- depending on the integration, these features might need to be enabled via support / Customer Success Manager (CSM)
- Feedback is more than welcome via Productboard or Zendesk
In this stage, the integration is considered production-ready. They are fully supported by LeanIX support, and documentation is regarded as sufficient to onboard users independently.
Aspects to note:
- Integrations in this stage are feature-complete for the communicated scope. There are no backward incompatibilities
- LeanIX fully supports these integrations & APIs, and the normal SLA applies
- These integrations are self-configurable via the integrations page in the administration section
Want to see some examples of how the APIs above can be utilized? We got you covered - in the tutorials section, you find some detailed step-by-step guides on the most common cases our APIs are used for:
Updated 9 days ago