[deep-report] Fix OTLP traces collector 404 endpoint drift (was 401 on 05-17)

[github-actions]

Context

The 2026-05-20 audit (discussion #33643) flagged that OTLP exports now return 404 Not Found across nearly every Claude/Copilot agent step, e.g.:

traces export: failed to send to ***: 404 Not Found (body: (empty))

On 2026-05-17 the symptom was 401 Unauthorized — an auth fix landed (good), but the new 404 suggests the collector route / path is stale. Every Contribution Check, Auto-Triage, and other agent step logs this, which silently undermines all GenAI telemetry dashboards.

This is distinct from #33740, which is about INPUT_JOB_NAME normalization inside the conclusion-span builder. This issue is about the collector URL endpoint itself.

Quick-win task

1. Decode GH_AW_OTLP_ENDPOINTS from a recent failing run (e.g. §26183420845).
2. Hit each endpoint with curl from a CI runner; confirm which path 404s.
3. Update the collector URL (likely in the OTLP setup action or workflow env) to the current /v1/traces route the collector expects.
4. Re-run one workflow and verify traces export succeeds.

Success criteria

• 0 traces export: failed lines in the next agent run.
• Grafana GenAI / Sentry OTLP dashboards begin populating again.

References

• Audit: discussion #33643
• Sibling open issue: #33740 (INPUT_JOB_NAME — different layer)
• Estimated effort: < 2h

Generated by 🔬 DeepReport - Intelligence Gathering Agent · ● 17.9M · ◷

• expires on May 23, 2026, 4:03 PM UTC

[github-actions]

This issue was automatically closed because it expired on 2026-05-23T16:03:29.778Z.

Closed by Workflow