What we shipped last month
Custom Component Relationships
OpsLevel's Component Relationship feature enhances your software catalog by enabling more accurate modeling of connections between entities. This helps provide a comprehensive view of your software ecosystem, making it easier to understand and manage key information about your software.
Relationships can be defined between Component Types and other Component Types or Teams. Users can seamlessly link to related catalog objects within component fields by configuring these connections. This provides quick access to crucial information, facilitating better comprehension and quicker action.
Examples:
- Services may have a Support Team in addition to their Owner.
- You may have a number of different component types that higher-level components can depend on, like: Libraries, Pipelines, Features, and Configurations.
- Adding Environment as a component type can now allow a richer relationship where components point to the Environments they're deployed on. This way, you will be able to query components more easily per environment.
Read the docs to learn more.
Customizable Data Mapping
Custom Integrations each come equipped with a webhook endpoint that allows you to push data to OpsLevel. Users can then manipulate this data via Extraction and Transform Configurations to update Custom Properties on existing Component Types.
This capability enables you to fully customize how data from external tools is incorporated into your catalog rather than relying on pre-defined integrations.
Why is Customizable Data Mapping Important?
- Flexibility: Map data from various sources (like Wiz, Jira, or Datadog) to OpsLevel in the way that makes the most sense for your organization.
- Faster Integration: Bring in data from tools that OpsLevel doesn't natively support, without waiting for bespoke development.
- Improved Data Visibility: Control where your data is stored and how it's displayed, giving you a clearer picture of your components and systems.
Watch the demo below to see how this works with the CloudZero + OpsLevel integration to bring cloud costs into the app, or read the docs.
Additional updates
- Azure storage account tags now saved on child resources
- GitHub Code Issues are now removed from OpsLevel when the source issue is closed
- New Azure resources: VPN Gateways, Service Bus Namespaces, Service Bus Queues
- You can now trigger Actions via API
- Service templates can write directly to Bitbucket
You can see all the product release notes here or book some time with our team to get a live demo of OpsLevel.