gnodet opened a new issue, #13567: URL: https://github.com/apache/maven/issues/13567
## Context The [OpenTelemetry Maven extension](https://github.com/open-telemetry/opentelemetry-java-contrib/tree/main/maven-extension) (v1.60.0-alpha) captures per-mojo spans as an EventSpy. Maven's `BuildReport` captures overlapping data (per-mojo timing, module execution, downloads). The two aren't competing — OTel is for distributed tracing backends (Jaeger, Grafana Tempo), while `build-report.json` is for local consumption. ## Proposal Add optional fields to `MojoReport` and `ModuleReport`: ```java @Nullable String traceId(); @Nullable String spanId(); ``` These are populated only when the OTel extension (or any other tracing extension) sets them via a well-defined mechanism (e.g., MDC keys `otel.trace_id` and `otel.span_id`, or a dedicated API). This lets tools correlate the local JSON report entry with a specific span in a distributed trace — useful for CI observability dashboards. ## Priority Nice-to-have. Low effort, high interoperability value. ## Related - #12695 — Build report PR - #12571 — Build output overhaul tracking issue <!-- AI-Agent-Disclosure --> > 🤖 Drafted with Claude Code (Claude Opus 4.6). Reviewed and confirmed by @gnodet before submission. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
