Push run and worker metrics via OTLP

Metrics today come from the pull-based Prometheus exporter, which still needs an Admin key (a read-only role is Planned), or from the Datadog-only integration. Teams that are standardizing on OpenTelemetry collectors want Spacelift to push run, queue, and worker metrics over OTLP to any backend, without running and securing an exporter per cluster.

This is related to, but separate from, Richer native Prometheus metrics: full exporter coverage, run timing, worker/queue metrics. That post is about making the pull exporter complete. This one is about a push path over OTLP.

Also related: Expose usage metrics through Datadog.

Customers also want better queued-run and queue-time monitoring than they get from the current run count metrics.

What this should include:

• The same endpoint config as the OTLP trace export request, so one destination can take traces and metrics.
• Metrics for run count, outcome, and duration by phase, queue time, drift runs as a separate series, worker pool busy/idle/capacity, and usage minutes. Labels for stack, space, worker pool, and run type.
• Keep the Prometheus exporter as the pull option. OTLP is the push option, not a replacement.