Ctrlk
Sign UpGet a DemoContact Us
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Export Efficiency (DORA Metrics)

Learn how to export Efficiency (DORA) metrics using the Harness AIDI Reports API.

Harness AIDI provides APIs to export Efficiency (DORA metrics) in CSV format for teams and organization trees. There are two available APIs:

  • V2 Efficiency Export API (recommended): Asynchronous export API for scalable DORA metric exports.

  • Legacy Reports API: Synchronous CSV export API maintained for backward compatibility.

The V2 Efficiency Export API provides asynchronous exports for DORA metrics including Lead Time for Changes (LTTC), Deployment Frequency (DF), Mean Time to Restore (MTTR), and Change Failure Rate (CFR).

Authentication

All requests require the following headers:

Header
Value

authorization

ApiKey <YOUR_SEI_API_KEY>

Content-Type

application/json

You must also include the following query parameters on all requests:

Parameter
Description

projectIdentifier

Harness project identifier

orgIdentifier

Harness organization identifier

Export workflow

Creates a new asynchronous Efficiency export job.

# Replace BASE_URL with your Harness cluster URL <a href="#replace-baseurl-with-your-harness-cluster-url" id="replace-baseurl-with-your-harness-cluster-url"></a>
POST {BASE_URL}/v2/insights/efficiency/exports
{
  "scope": {
    "teamId": "team_abc123",        // String identifier; use either teamId OR orgTreeName (not both)
    "orgTreeName": "string",
    "orgIdentifier": "string",      // Required when using orgTreeName
    "projectIdentifier": "string",
    "managerEmailId": "string"      // Optional; scope export to a manager's teams
  },
  "dateRange": {
    "start": "2026-01-01",          // Required (yyyy-MM-dd)
    "end": "2026-03-31"             // Required (yyyy-MM-dd)
  },
  "metricGroups": ["lttc", "df", "mttr", "cfr", "summary"], // Use metricGroups OR metrics (mutually exclusive)
  "metrics": ["LTTC_Mean_Days", "DF_Deployment_Count", "CFR_Failure_Rate_Percent"], // Alternative to metricGroups
  "options": {
    "granularity": "MONTHLY",       // Required
    "aggregation": "mean",          // Optional; mean, median, p90, p95
    "format": "csv",                // Optional; csv, json
    "compression": "gzip",          // Optional
    "workCategoryFilter": ["BUGS", "FEATURES"] // Optional; lttc only. Values: ["ALL"] (default, no split) | ["BUGS"] | ["FEATURES"] | ["BUGS","FEATURES"] (both)
  }
}

The following request fields are available:

Field
Description

scope.teamId

Export data for a specific team. Use either teamId or orgTreeName, not both.

scope.orgTreeName

Export data for an organization tree.

scope.managerEmailId

Optional. Scopes the export to a manager's teams.

dateRange.start

Export start date (yyyy-MM-dd).

dateRange.end

Export end date (yyyy-MM-dd).

metricGroups

Supported DORA metrics such as Lead Time for Changes (lttc), Deployment Frequency (df), Mean Time to Restore (mttr), Change Failure Rate (cfr), or aggregate DORA summary metrics (summary). Use metricGroups or metrics, not both.

metrics

Individual metric columns such as LTTC_Mean_Days or DF_Deployment_Count. Use metrics or metricGroups, not both.

options.granularity

Reporting interval (WEEKLY, MONTHLY, QUARTERLY).

options.aggregation

Aggregation method (mean, median, p90, p95).

options.format

Export file format (csv, json).

options.compression

Export compression format (gzip).

options.workCategoryFilter

Optional. Applies only when lttc is included in metricGroups/metrics. Splits Lead Time for Changes by work item category. Values: ["ALL"] (default, no split), ["BUGS"], ["FEATURES"], or ["BUGS","FEATURES"] (both).

Available metric groups

The following Efficiency metric groups are available:

Metric Group
Included Metrics

lttc

PLANNING, CODING, REVIEW, BUILD, DEPLOY, LTTC

work_items

TOTAL_WORK_ITEMS, PR_ASSOCIATIONS, PERCENTAGE_PR_ASSOCIATED

deployment_frequency

DEPLOYMENT_FREQUENCY

cfr

TOTAL_SUCCESS, TOTAL_FAILURES, CFR

mttr

MTTR

rating

OVERALL_RATING

Poll the export until the status changes to COMPLETED.

The following export statuses are available:

Status
Description

QUEUED

Export queued.

PROCESSING

Export in progress.

COMPLETED

Export ready.

FAILED

Export failed.

Downloads the generated CSV export file.

Downloads are gzip-compressed by default and export responses include team hierarchy information where applicable.

Example 2: Export Team Efficiency Report (DORA Metrics)

  • Default Calculation Type: If calculationType is not specified for Efficiency metrics, it defaults to MEAN.

To configure Efficiency metrics with EfficiencyRequestDto:

  • metrics (required): List of efficiency metric names to include in the export.

  • calculationType (optional): Aggregation method (defaults to MEAN).

The following Efficiency (DORA) metrics are available:

Metric Name
Context
Unit
Description

LEAD_TIME_FOR_CHANGES

Lead Time for Changes

Days (CSV contains numeric values without unit labels)

Measures the time from code commit to production deployment. Key indicator of delivery speed and process efficiency. Lower lead times indicate faster feature delivery and more agile development. Industry benchmark: Elite performers achieve lead times under 1 day.

DEPLOYMENT_FREQUENCY

Deployment Frequency

Deployments per time period (affected by granularity)

Tracks how often code is deployed to production. Indicates team's ability to deliver value continuously. Higher frequency suggests better automation and CI/CD maturity. Example: 20 means 20 deployments per week (if granularity is weekly). Industry benchmark: Elite performers deploy multiple times per day.

CHANGE_FAILURE_RATE

Change Failure Rate

Percentage (0–100, CSV contains numeric values without unit labels)

Percentage of deployments that cause failures in production. Measures quality and stability of releases. Lower rates indicate better testing, quality assurance, and deployment practices. Industry benchmark: Elite performers maintain CFR below 15%.

MEAN_TIME_TO_RESTORE

Mean Time to Restore (MTTR)

Days (CSV contains numeric values without unit labels)

Time to recover from a production failure or incident (aggregated using calculationType). Indicates team's incident response capability and system resilience. Lower MTTR suggests effective monitoring, alerting, and rollback procedures. Industry benchmark: Elite performers restore service in under 1 hour.

OVERALL_DORA

Overall DORA Score

Score/Rating (implementation-specific)

Composite metric combining all four DORA metrics. Provides holistic view of team's DevOps performance. Used to classify teams as Elite, High, Medium, or Low performers. Based on Google's DORA State of DevOps research.

PreviousExport Insights
NextExport Sprint Metrics

Last updated

Was this helpful?