Recent commits introduced a user-facing wording inconsistency in OTLP tracing errors.
Design Drift Findings
1. OTLP endpoint parse error says "OLTP" instead of established "OTLP"
Commit(s):
New pattern (introduced by commit):
// x-pack/filebeat/otel/trace.go:191
return nil, fmt.Errorf("can't parse OLTP endpoint URL: %w", err)
Existing pattern (established elsewhere):
// x-pack/filebeat/otel/trace.go:108
return nil, fmt.Errorf("unsupported OTLP traces protocol %q (expected grpc or http/protobuf)", cfg.Protocol)
// x-pack/filebeat/otel/exporter_factory.go:64
// - OTEL_EXPORTER_OTLP_ENDPOINT: Required. The OTLP endpoint URL.
Location of new pattern:
x-pack/filebeat/otel/trace.go:191
Location of existing pattern:
x-pack/filebeat/otel/trace.go:108
x-pack/filebeat/otel/exporter_factory.go:63-65
User impact:
Users troubleshooting OTLP exporter configuration can encounter mixed terms ("OLTP" vs "OTLP") for the same concept, which reduces clarity and makes log/error searching less reliable.
Suggested Actions
Duplicate Check
- Checked
/tmp/previous-findings.json: no existing OTLP/OLTP item.
- Searched
elastic/beats issues and PRs for "can't parse OLTP endpoint URL" and "OLTP endpoint" + "OTLP": no matching tracking issue found.
What is this? | From workflow: UX Design Patrol
Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.
Recent commits introduced a user-facing wording inconsistency in OTLP tracing errors.
Design Drift Findings
1. OTLP endpoint parse error says "OLTP" instead of established "OTLP"
Commit(s):
fb0542fabb73d5e0445295df5deb3da41f4a6467(CEL input: Add OTel tracing, PR CEL input: Add OTel tracing #48440)New pattern (introduced by commit):
Existing pattern (established elsewhere):
Location of new pattern:
x-pack/filebeat/otel/trace.go:191Location of existing pattern:
x-pack/filebeat/otel/trace.go:108x-pack/filebeat/otel/exporter_factory.go:63-65User impact:
Users troubleshooting OTLP exporter configuration can encounter mixed terms ("OLTP" vs "OTLP") for the same concept, which reduces clarity and makes log/error searching less reliable.
Suggested Actions
"can't parse OLTP endpoint URL: %w"to"can't parse OTLP endpoint URL: %w"inx-pack/filebeat/otel/trace.go.x-pack/filebeat/otel/*to ensure acronym consistency across user-facing messages.Duplicate Check
/tmp/previous-findings.json: no existing OTLP/OLTP item.elastic/beatsissues and PRs for"can't parse OLTP endpoint URL"and"OLTP endpoint" + "OTLP": no matching tracking issue found.What is this? | From workflow: UX Design Patrol
Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.