OTEL-044: OTLP gRPC exporter endpoint has http(s):// scheme
Severity: deny (blocking)
Rule Details
The otlp exporter speaks gRPC, and its endpoint field expects a bare host:port. If you include an http:// or https:// prefix, the exporter's gRPC dialer fails at startup with a confusing invalid target error and the pipeline never starts. Use the otlphttp exporter if you need a URL scheme.
This rule fires when an otlp exporter's endpoint starts with http:// or https://.
Options
This rule has no options.
Examples
Incorrect
exporters:
otlp/backend:
endpoint: https://backend.example.com:4317 # scheme not allowed
Correct
exporters:
otlp/backend:
endpoint: backend.example.com:4317
tls:
insecure: false
When Not To Use It
Never — this will fail at Collector start-up.
Related Rules
- OTEL-045 — OTLP gRPC endpoint missing port number
- OTEL-046 — OTLP HTTP endpoint missing URL scheme
- OTEL-047 — OTLP HTTP exporter using gRPC port 4317
Version
Available since augur v0.1.0.
Further Reading
Resources
- Rule source:
policy/main/exporter.rego