Integration · CI / CD

GitLab CI

Pipeline duration, runner load, success rate.

What gets collected

The GitLab REST API plus a webhook on pipeline events. Per-project / per-runner aggregation.

Requirements

  • GitLab 14+
  • token scope read_api
  • pipeline events webhook

Key metrics

Collected out of the box. Every metric is available in dashboards, alerts and PromQL.

gitlab.pipeline.durationgitlab.runner.loadgitlab.job.success.rategitlab.queue.time

Setup steps

  1. 1Token with read_api
  2. 2Webhook URL on /api/v1/integrations/gitlab/hook

After install

  • · Metrics show up on the dashboard within 15-30 seconds
  • · Integration labels flow into filters automatically
  • · Dashboard presets for common metrics are available in the editor
More in the docs
GitLab CI
Open the guide →

Frequently asked questions

What does Unimoni collect from GitLab CI?
Pipeline duration, runner load, success rate. Every metric lands in the same TSDB as the rest of your stack, so you can build dashboards and alerts across GitLab CI and everything else in one place.
How long does it take to connect GitLab CI?
Usually a few minutes: a handful of steps, no code changes. Metrics show up on your dashboards within 15–30 seconds of the first scrape.
What access does the GitLab CI integration need?
Only the minimum listed under Requirements above — a scoped token or role, nothing more. Unimoni asks for the least privilege each system supports.
Is GitLab CI monitoring available self-hosted and on the free plan?
Yes. Every integration works identically on Unimoni Cloud and self-hosted, and is included from the free tier up.

Similar integrations