Barnabas Busa f568ab9931 internal/telemetry: add gRPC transport for OTLP trace export (#33941) ... ## Summary - Add `grpc://` and `grpcs://` URL scheme support for OTLP trace export alongside existing `http://`/`https://` - The OTLP spec defines two transports: HTTP (port 4318) and gRPC (port 4317). Many observability backends (Jaeger, Tempo, Datadog) prefer gRPC for lower overhead - Both `otlptracehttp` and `otlptracegrpc` return `*otlptrace.Exporter`, so only exporter construction changes — everything downstream (batch processor, tracer provider, lifecycle) is untouched - Update flag usage strings to be transport-agnostic ## Example usage ``` geth --rpc.telemetry --rpc.telemetry.endpoint grpc://localhost:4317 geth --rpc.telemetry --rpc.telemetry.endpoint grpcs://tempo-grpc.example.com:443 ``` --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>		2026-04-21 14:48:21 +02:00
..
tracesetup	internal/telemetry: add gRPC transport for OTLP trace export (#33941)	2026-04-21 14:48:21 +02:00
telemetry.go	internal/telemetry: don't create internal spans without parents (#33780)	2026-02-17 14:12:42 +01:00
telemetry_test.go	internal/telemetry: don't create internal spans without parents (#33780)	2026-02-17 14:12:42 +01:00