Pipeline analytics

Analytics mode returns aggregated metrics for pipelines in all states, including in-progress pipelines, with data typically available within ten minutes.

To query individual pipeline records, use Pipelines.

Allowed scopes

To aggregate pipelines across multiple groups or projects, use a list with the in operator. For more information, see multiple groups and projects.

Query filters

Use these fields in the query parameter to filter your results.

Finished at

Description: Filter pipelines by their finish date.

Allowed value types:

• AbsoluteDate (in the format YYYY-MM-DD)
• RelativeDate (in the format <sign><digit><unit>, where sign is +, -, or omitted, digit is an integer, and unit is one of d (days), w (weeks), m (months) or y (years))

Notes:

• For the = operator, the time range is considered from 00:00 to 23:59 in the user’s time zone.

Ref

Description: Filter pipelines by the Git ref (branch or tag name) they ran on.

Allowed value types:

• String
• List (use in or not in operator for multiple values)

Notes:

• != and not in return only pipelines that have a ref. Pipelines without one are left out, so ref != "main" is not the same as every pipeline except those on main.

Source

Description: Filter pipelines by their trigger event.

Allowed value types:

• String
• List (use in or not in operator for multiple values)

Notes:

• != and not in return only pipelines that have a source. Pipelines without one are left out.
• Excluding a source that GitLab does not recognize excludes nothing. Validation of source values is proposed in issue 629846.

Started at

Description: Filter pipelines by their start date.

Allowed value types:

• AbsoluteDate (in the format YYYY-MM-DD)
• RelativeDate (in the format <sign><digit><unit>, where sign is +, -, or omitted, digit is an integer, and unit is one of d (days), w (weeks), m (months) or y (years))

Notes:

• For the = operator, the time range is considered from 00:00 to 23:59 in the user’s time zone.

Status

Description: Filter pipelines by their CI/CD status.

Allowed value types:

• Enum, one of canceled, canceling, created, failed, manual, pending, preparing, running, scheduled, skipped, success, waiting_for_callback, or waiting_for_resource
• List (use in or not in operator for multiple values)

Dimensions

Metrics

A pipeline is considered finished when it has completed processing and reached a final state: successful, failed, canceled, or skipped.

Sort fields

Sort by any field included in your selected dimensions or metrics. For more information, see analytics mode sorting.

Examples

• Pipeline success and failure rates by ref for the last 30 days:

  yaml

  ```glql
  title: "Pipeline success and failure rates by branch (last 30 days)"
  display: table
  mode: analytics
  query: type = Pipeline and project = "gitlab-org/gitlab" and finished >= -30d
  dimensions: ref as "Ref"
  metrics: totalCount as "Total", successRate as "Success rate", failureRate as "Failure rate"
  sort: totalCount desc
  ```

• Pipelines with any status other than success, off the default branches, for the last 30 days:

  yaml

  ```glql
  title: "Pipelines not successful, off the default branches (last 30 days)"
  display: table
  mode: analytics
  query: type = Pipeline and project = "gitlab-org/gitlab" and finished >= -30d and status != success and ref not in ("main", "master")
  dimensions: ref as "Ref"
  metrics: totalCount as "Pipelines", failureRate as "Failure rate"
  sort: totalCount desc
  limit: 10
  ```

• Pipeline duration trend by week for a specific ref:

  yaml

  ```glql
  title: "Weekly pipeline duration trend for master"
  display: table
  mode: analytics
  query: type = Pipeline and project = "gitlab-org/gitlab" and ref = "master" and finished >= -90d
  dimensions: finished as "Week"
  metrics: totalCount as "Total", durationQuantile as "p95 duration (s)"
  sort: finished desc
  ```

• Median and p95 pipeline duration by week:

  yaml

  ```glql
  title: "Median and p95 pipeline duration by week"
  display: table
  mode: analytics
  query: type = Pipeline and project = "gitlab-org/gitlab" and finished >= -90d
  dimensions: finished(weekly) as "Week", status as "Status"
  metrics: durationQuantile(0.5) as "Median", durationQuantile(0.95) as "p95", totalCount as "Total"
  sort: Median desc
  ```

• Overall pipeline metrics for a group, without grouping:

  yaml

  ```glql
  title: "Overall pipeline metrics for gitlab-org"
  display: table
  mode: analytics
  query: type = Pipeline and group = "gitlab-org" and finished >= -7d
  metrics: totalCount as "Total", successRate as "Success rate", failureRate as "Failure rate", canceledRate as "Canceled rate"
  ```

• Pipelines grouped by source and status, filtered to a date range:

  yaml

  ```glql
  title: "Pipelines by source and status (Q1 2026)"
  display: table
  mode: analytics
  query: type = Pipeline and project = "gitlab-org/gitlab" and finished >= "2026-01-01" and finished <= "2026-03-31"
  dimensions: source as "Source", status as "Status"
  metrics: totalCount as "Total"
  sort: totalCount desc
  ```

• Filter to specific refs and statuses across a group:

  yaml

  ```glql
  title: "Default branch pipeline outcomes across gitlab-org"
  display: table
  mode: analytics
  query: type = Pipeline and group = "gitlab-org" and finished >= -14d and ref in ("master", "main") and status in ("success", "failed")
  dimensions: project as "Project", status as "Status"
  metrics: totalCount as "Total", successRate as "Success rate"
  sort: totalCount desc
  limit: 20
  ```