Draft: feat: add operator-controlled OpenTelemetry tracing, metrics, and log export

Adrian Fernandez de la Torrerequested to merge
gitlab-community/gitlab-org/gitlab-runner:erdaref/feature/otel-observability into main

What does this MR do?

feat: add operator-controlled OpenTelemetry tracing, metrics, and log export

Introduce a full OpenTelemetry observability stack for GitLab Runner operators. This adds:

  • OTLP trace, metric, and log exporters configurable via runner config and environment variables
  • A logrus hook that forwards structured logs to the OTLP log endpoint
  • Job-level metrics (duration, status counters) exposed via the OTel SDK
  • HTTP request tracing for GitLab API calls in the network client
  • Integration with the Docker and Kubernetes executors
  • Documentation for configuration and usage

The feature is opt-in: when no OTel endpoint is configured, the runner behaves identically to before.

Why was this MR needed?

What's the best way to test this MR?

What are the relevant issue numbers?

Merge request reports