merge: bring the OTLP gRPC exporter rename forward from phase5-docs-deployment

Conflict in docker/telemetry/otel-collector-config.yaml, in the service
pipelines: this branch renamed the deprecated spanmetrics connector to
span_metrics and adds the statsd metrics pipeline, while upstream renamed the
deprecated otlp exporter to otlp_grpc. Both kept.

With both renames present the collector now starts with no deprecation
warnings at all, which was the point of the pair.
This commit is contained in:
Pratik Mankawde
2026-09-09 19:17:07 +01:00
2 changed files with 3 additions and 3 deletions

View File

@@ -106,7 +106,7 @@ The authoritative collector config lives in the repo at `docker/telemetry/otel-c
### 5.5.1 Development Configuration
The development collector enables an OTLP receiver on both gRPC (`0.0.0.0:4317`) and HTTP (`0.0.0.0:4318`), a single `batch` processor (1s timeout, batch size 100), and two exporters: a `logging` exporter for console debugging and `otlp/tempo` (insecure) for trace visualization. The single `traces` pipeline wires receiver → batch → both exporters.
The development collector enables an OTLP receiver on both gRPC (`0.0.0.0:4317`) and HTTP (`0.0.0.0:4318`), a single `batch` processor (1s timeout, batch size 100), and two exporters: a `logging` exporter for console debugging and `otlp_grpc/tempo` (insecure) for trace visualization. The single `traces` pipeline wires receiver → batch → both exporters.
### 5.5.2 Production Configuration

View File

@@ -121,7 +121,7 @@ connectors:
exporters:
debug:
verbosity: detailed
otlp/tempo:
otlp_grpc/tempo:
endpoint: tempo:4317
tls:
insecure: true
@@ -144,7 +144,7 @@ service:
traces:
receivers: [otlp]
processors: [resource/tier, resource/stripsdk, attributes/hash, batch]
exporters: [debug, otlp/tempo, span_metrics]
exporters: [debug, otlp_grpc/tempo, span_metrics]
metrics:
receivers: [span_metrics, statsd]
processors: [resource/tier, resource/stripsdk]