fix(otel): normalize OTEL endpoint env vars to prevent SDK parse errors

[jeffersonrodrigues92]

Summary

• Adds normalizeEndpointEnvVars() that prepends http:// to OTEL_EXPORTER_OTLP_*_ENDPOINT env vars when they contain bare host:port without a scheme
• Prevents the OTEL SDK's internal url.Parse() from logging noisy "parse url" errors
• Complements the existing normalizeEndpoint() which only handled the programmatic CollectorExporterEndpoint config field

Problem

The OTEL Go SDK (v1.42.0) reads endpoint env vars internally via envconfig.WithURL() → url.Parse(). When the env var contains host:port without a scheme (e.g. 10.10.0.202:4317), Go's URL parser fails:

"msg"="parse url" "error"="parse \"10.10.0.202:4317\": first path segment in URL cannot contain colon"

This happens independently of the programmatic WithEndpoint() path, which PR #362 already fixed. The SDK reads env vars before applying programmatic options, so bare host:port in env vars still caused the error.

Root Cause

The OTEL SDK's envconfig.go (lines 93-104) uses url.Parse() to read OTEL_EXPORTER_OTLP_ENDPOINT, OTEL_EXPORTER_OTLP_TRACES_ENDPOINT, and OTEL_EXPORTER_OTLP_METRICS_ENDPOINT. The error appears twice per startup (once for trace exporter, once for metric exporter).

Test plan

• 8 table-driven test cases × 3 env var keys = 24 subtests covering: bare host:port, hostname:port, http preserved, https preserved, whitespace trimming, empty value, whitespace-only, unset env var
• All existing tests pass
• go build ./commons/opentelemetry/... passes

🤖 Generated with Claude Code

[coderabbitai]

Caution

Review failed

Pull request was closed or merged during review

Walkthrough

The changes add environment variable normalization for OpenTelemetry OTLP endpoint configuration. During telemetry initialization, a new helper function processes three environment variables by trimming whitespace and prepending the HTTP scheme when endpoints lack http:// or https:// prefixes. This ensures the OTEL SDK receives properly formatted endpoint URLs. Corresponding test coverage validates the normalization behavior across various input scenarios including bare hostnames, existing schemes, and whitespace handling.

🚥 Pre-merge checks | ✅ 2

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The pull request title clearly summarizes the main change: normalizing OTEL endpoint environment variables to prevent SDK parse errors.
Description check	✅ Passed	The pull request description is comprehensive and well-structured, covering the summary, problem, root cause, and test plan sections thoroughly.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}