Delivery Insights
Delivery Insights is an alpha feature. It is disabled by default and must be opted into, it may contain bugs that become apparent once enabled, and it has not been tested across every OpenChoreo deployment topology. Its API and stored schema may change incompatibly in a later release without notice.
Delivery Insights reports the four DORA metrics — Deployment Frequency, Lead Time for Changes, Change Failure Rate and Mean Time to Recovery — for the components OpenChoreo deploys, at namespace, project or component scope, sliced by environment.
DORA Metrics
| Metric | Answers | Derived from |
|---|---|---|
| Deployment Frequency | How often do we ship? | Rollouts that reached a healthy state |
| Lead Time for Changes | How long from commit to running? | Commit authoring time to rollout ready time |
| Change Failure Rate | How often does shipping break something? | Failed rollouts, and incidents attributed to a rollout |
| Mean Time to Recovery | How long until we are healthy again? | Incidents, from trigger to resolution |
Each metric comes back with its value, a DORA classification (Elite, High, Medium, Low), a trend against the previous window of equal length, and a time-bucketed series at daily, weekly or monthly granularity.
The Observer folds delivery events and incidents into durable facts on a timer, then pre-computes the rollups the API serves. Aggregation runs every five minutes, so a deployment appears in the metrics on the next tick rather than immediately.
Prerequisites
- An observability plane installed and registered as an
ObservabilityPlane. See Observability & Alerting. - The observability-logs-opensearch logs module, version
0.6.0or later. It is the only logs module that serves the delivery events sweep today.
Enabling Delivery Insights
Two independent flags, both off by default, and both are required. One collects the data; the other shows the page.
Step 1: Collect the metrics in the Observer
helm upgrade openchoreo-observability-plane oci://ghcr.io/openchoreo/helm-charts/openchoreo-observability-plane \
--version 1.3.0 \
--namespace openchoreo-observability-plane \
--reuse-values \
--set observer.featurePreview.deliveryInsights.enabled=true
The Observer creates its delivery insights tables on startup and begins aggregating. While the flag is off it does not open the store at all, so an installation that never enables the feature carries none of its tables.
Step 2: Show the page in the portal
helm upgrade openchoreo-control-plane oci://ghcr.io/openchoreo/helm-charts/openchoreo-control-plane \
--version 1.3.0 \
--namespace openchoreo-control-plane \
--reuse-values \
--set backstage.features.deliveryInsights.enabled=true
With this off, Delivery Insights is absent from the portal navigation and the page renders a disabled notice if reached by URL.
Access
Reading the metrics requires the deliveryinsights:view action. The portal, the read API and the MCP tools all enforce it. By default it is granted by the admin, platform-engineer, developer and sre roles.
Querying from an Agent
The observability plane MCP server exposes the metrics as two tools, so an agent can answer delivery questions without going through the portal. Both are served from the Observer's /mcp endpoint and enforce the same deliveryinsights:view action as the portal.
| Tool | Returns |
|---|---|
query_dora_metrics | The four metrics for a scope and window: value, classification, trend and a time-bucketed series |
query_dora_deployments | The individual rollouts behind those numbers, with project, component, environment, commit, outcome and lead time |
Both require namespace, start_time and end_time, and narrow with project, component and environment. query_dora_metrics also takes granularity and a metrics list to compute a subset; query_dora_deployments takes limit and sort_order.
Classification depends on the length of the window. The same rollouts can read Elite over a week and High over a month, because the per-day rate falls as the window widens. Compare like windows.
See MCP Servers for connecting an assistant to the observability plane.
Configuration Reference
Observability Plane
| Value | Default | Description |
|---|---|---|
observer.featurePreview.deliveryInsights.enabled | false | Collect delivery metrics. Maps to FEATURE_PREVIEW_DELIVERY_INSIGHTS_ENABLED |
Control Plane
| Value | Default | Description |
|---|---|---|
backstage.features.deliveryInsights.enabled | false | Show the Delivery Insights page. Maps to OPENCHOREO_FEATURES_DELIVERY_INSIGHTS_ENABLED |