Integration that allows to:

• Visualize and monitor metrics collected via Gitlab Runners through Prometheus
• Validate that the Gitlab Runner can connect to Gitlab

See the Gitlab Runner documentation for more information about Gitlab Runner and its integration with Prometheus

Follow the instructions below to install and configure this check for an Agent running on a host. For containerized environments, see the Autodiscovery Integration Templates for guidance on applying these instructions.

The Gitlab Runner check is included in the Datadog Agent package, so you don't need to install anything else on your Gitlab servers.

Edit the gitlab_runner.d/conf.yaml file, in the conf.d/ folder at the root of your Agent's configuration directory, to point to the Runner's Prometheus metrics endpoint and to the Gitlab master to have a service check. See the sample gitlab_runner.d/conf.yaml for all available configuration options.

Note: The allowed_metrics item in the init_config section allows to specify the metrics that should be extracted.

Remarks: Some metrics should be reported as rate (i.e., ci_runner_errors)

Run the Agent's status subcommand and look for gitlab_runner under the Checks section.

See metadata.csv for a list of metrics provided by this integration.

The Gitlab Runner check does not include any events.

The Gitlab Runner check provides a service check to ensure that the Runner can talk to the Gitlab master and another one to ensure that the local Prometheus endpoint is available.

Need help? Contact Datadog support.