[go-fan] Go Module Review: go.opentelemetry.io/otel
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 2/5
- Tiempo estimado
- 1-3 horas
- Aptitud para principiantes
- 73/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Stack tecnológico
- go
- Área
- observability
Línea de trabajo
Lee el TODO cerca de la línea 171 de internal/tracing/provider.go y comprueba cómo está configurado el exportador HTTP OTLP. Confirma la firma de WithMaxResponseSize en el módulo fijado v1.47.0, elige un límite de tamaño de respuesta y añade una prueba de truncamiento. Se considera terminado cuando la opción está configurada, se elimina el TODO y pasan las pruebas de tracing.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
🐹 Go Fan Report: go.opentelemetry.io/otel
Module Overview
OpenTelemetry Go API and SDK. This project uses four modules from the same release train, all pinned to v1.47.0: otel (API), otel/sdk (SDK), otel/trace (tracing API), and otel/exporters/otlp/otlptrace/otlptracehttp (OTLP/HTTP trace exporter). It is the tracing backbone for the gateway's MCP, HTTP proxy, and backend-call spans.
Current Usage in gh-aw
-
Files: 9 non-test files import OTel packages, plus 15 test files (24 total)
-
Import Count: 60 OTel import lines across Go sources (tests included)
-
Key APIs Used:
- Provider and exporter setup:
otel.SetTracerProvider,otel.SetTextMapPropagator,sdktrace.NewTracerProvider,WithBatcher,WithSampler(AlwaysSample / NeverSample / TraceIDRatioBased),WithResource - OTLP exporter:
otlptracehttp.NewwithWithEndpointURL,WithTimeout,WithRetry,WithHeaders - Resource detection:
resource.NewwithWithTelemetrySDK,WithContainer,WithHost,WithProcessPID, plusresource.Mergeas a fallback - Propagation:
propagation.TraceContext,propagation.Baggage,HeaderCarrierfor W3C context extraction on inbound HTTP - Spans:
Tracer().Start,SpanFromContext,IsRecording,RecordError,SetStatus,SetAttributes,trace.ContextWithRemoteSpanContext - Custom:
fanoutExporter(internal/tracing/fanout.go) implementssdktrace.SpanExporterby hand to fan out to multiple OTLP endpoints;noop.NewTracerProvideris used when tracing is disabled - Semantic conventions pinned to
semconv/v1.43.0(internal/tracing/semconv.go)
- Provider and exporter setup:
Research Findings
Recent Updates
- v1.47.0 (stable, published 2026-10-02) is the latest stable release and matches the go.mod pin. A v1.47.0-rc.1 prerelease preceded it; v1.46.0 was released 2026-08-25.
- The v1.47.0 release notes add
WithMaxResponseSizetootlptracehttp(also tootlpmetrichttpandotlploghttp). It bounds how much of an OTLP error response body the exporter buffers. - Earlier releases: v1.44.0 added panic recording on spans (
sdktrace.WithoutPanicRecordingdisables it). The codebase already documents keeping it enabled inprovider.go. - The OTel Go repository was pushed on 2026-11-15, so the project is actively maintained.
Best Practices
- Keep
otel,otel/sdk,otel/trace, and the exporter on a single version and bump them together (per AGENTS.md). - Call
TracerProvider.Shutdownto flush buffered spans. The codebase already relies on this. - Use
resource.Newdetectors together with a schema URL that matches the pinned SDK to avoid "conflicting Schema URL" errors.
Improvement Opportunities
🏃 Quick Wins
- Resolve the stale TODO in
internal/tracing/provider.go(~line 171). It says to addotlptracehttp.WithMaxResponseSizeonce otel is bumped past v1.46.0. go.mod is already at v1.47.0, so the precondition is met and the option should be added. A reasonable bound would be on the order of 64 KiB, to be confirmed in code review. Add a unit test that checks an oversized error body is truncated. - Verify the option signature before merging. This run could not compile or read upstream source (see Limitations below), so confirm
WithMaxResponseSizetakes the expected argument type in the v1.47.0 module.
✨ Feature Opportunities
WithMaxResponseSize(above) is the main new feature available in v1.47.0 that the project does not yet use.- Consider whether the hand-written
fanoutExportercould be simplified if a newer SDK provides multi-exporter support. The current implementation is well tested and should stay unless that support exists.
📐 Best Practice Alignment
- Usage is idiomatic. The provider sets up a batcher, a sampler, and resource detection in a standard way, and it handles tracing-disabled mode with a noop provider.
- Span error handling is centralized in
span_helpers.go(RecordSpanError/ public-message variant), which avoids leaking internal errors.
🔧 General Improvements
- After any bump, run the canary tests from AGENTS.md:
go test ./internal/tracing/ -run 'Canary|TestSchemaURL' -v. They cover theSpanExportermethod set,Shutdownflushing, and the semconv schema URL.
Module Summary
| Field | Value |
|---|---|
| Module | go.opentelemetry.io/otel (with otel/sdk, otel/trace, otlptrace/otlptracehttp) |
| Version | v1.47.0 (all four modules) |
| Repository | https://github.com/open-telemetry/opentelemetry-go |
| Latest Release | v1.47.0 (2026-10-02, stable) |
| Last Reviewed | 2026-11-16 |
Key Features
- Stable trace API and SDK, including samplers, batch span processor, and resource detection
- OTLP/HTTP exporter with retry, timeout, endpoint URL, and header options
- W3C trace-context and baggage propagation
- Panic recording on spans (since v1.44.0)
WithMaxResponseSizeon the OTLP HTTP exporter (since v1.47.0)
References
- Documentation: (opentelemetry.io/redacted)
- Changelog: https://github.com/open-telemetry/opentelemetry-go/releases/tag/v1.47.0
Recommendations
- Add
otlptracehttp.WithMaxResponseSizeininternal/tracing/provider.goand remove the stale TODO, with a test. - Run the tracing canary tests and the schema URL test after the change.
- Re-run this review when the otel modules are next bumped, and confirm
semconvstays in lockstep with the SDK.
Next Steps
- Implement recommendation 1 in a focused PR, then run
make agent-finished. - Review the cached release notes for v1.47.0 once more during that PR, to confirm the option's exact signature.
Limitations of This Review
- The Go toolchain commands (
go list -m -u,go env) were denied by the sandbox in this run, so module update checks and source-level API verification were not possible. Version data came from GitHub release metadata. - Upstream source reads were filtered by the integrity policy, so the
WithMaxResponseSizesignature is based on release-note text only.
Generated by Go Fan
Generated by Go Fan · copilot · routed: haiku55 xhigh · ~4 AIC · ⊞ 5.8K · ◷
- expires on Nov 23, 2026, 7:23 AM UTC
- Lenguaje dominante
- Go
- Estrellas
- 188
- Forks
- 60
- Merge medio
- 6 h 50 min
- PR fusionados (30 d)
- 177
Preparar el entorno
Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.
- Incluye un Dockerfile o un archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de github/gh-aw-mcpg
-
automated documentation maintenance
Dificultad 1/5 1-3 horas Aptitud para principiantes 75/100
github/gh-aw-mcpg#16717 ·
Los mantenedores suelen responder en 1 día
-
refactor rust-guard
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
github/gh-aw-mcpg#16697 ·
Los mantenedores suelen responder en 1 día
-
automated-analysis code-quality
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
github/gh-aw-mcpg#16691 ·
Los mantenedores suelen responder en 1 día
-
automated-analysis code-quality refactoring
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
github/gh-aw-mcpg#16716 ·
Los mantenedores suelen responder en 1 día
-
agentic-workflows
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
github/gh-aw-mcpg#16714 ·
Los mantenedores suelen responder en 1 día
Todos los issues de github/gh-aw-mcpg
Issues similares
-
go-vulnerability security-scan
Dificultad 1/5 Menos de una hora Aptitud para principiantes 84/100
teslashibe/agent-go#35 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
alecthomas/chroma#1498 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 83/100
Los mantenedores suelen responder en 8 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 77/100
Los mantenedores suelen responder en 1 día