eblume/blumeops
1
1
Fork 0
Code Issues Pull requests Projects Releases 83 Packages Wiki Activity Actions

Fix OTEL metrics exporter warnings in Dagger builds

Browse source 
The Dagger engine shim sets OTEL_METRICS_EXPORTER before our module
loads, so os.environ.setdefault was a no-op. Switch to a hard override.
Remove the redundant workflow-level env var since the fix belongs in
the module.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Erich Blume 2026-04-13 08:11:15 -07:00
commit ab834b641a
3 changed files with 7 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

4
.forgejo/workflows/build-container.yaml
View file

@ -73,10 +73,6 @@ jobs:
needs: detect
if: needs.detect.outputs.dagger != '[]'
runs-on: k8s
env:
# Disable Python SDK OTLP metrics exporter — the Dagger engine's local
# OTLP endpoint returns 500s, causing ~9s retry cycles per minute.
OTEL_METRICS_EXPORTER: none
strategy:
matrix:
container: ${{ fromJson(needs.detect.outputs.dagger) }}

1
docs/changelog.d/+dagger-otel-metrics-fix.bugfix.md Normal file
View file

@ -0,0 +1 @@
Fix OTEL metrics exporter warnings in Dagger builds by hard-overriding the env var before SDK init.

9
src/blumeops/main.py
View file

@ -1,9 +1,12 @@
import os
from pathlib import Path
# Disable OTLP metrics exporter before the Dagger SDK initializes OpenTelemetry.
# The Dagger engine's local OTLP endpoint returns 500s, causing ~11s retry delays.
os.environ.setdefault("OTEL_METRICS_EXPORTER", "none")
# Force-disable OTLP metrics exporter before the Dagger SDK initializes
# OpenTelemetry. The engine shim may set OTEL_METRICS_EXPORTER=otlp before
# our module loads, so setdefault won't work — we need a hard override.
# Without this, the engine's local OTLP endpoint returns 500s on metrics,
# causing ~9s retry cycles per pipeline step.
os.environ["OTEL_METRICS_EXPORTER"] = "none"
import dagger
from dagger import dag, function, object_type