OTLP-Exporter - Phase 2

[aryamohanan]

Summary – Phase 2

Phase 2 focuses on completing the remaining OTLP exporter functionality required for customer readiness. This includes implementing the remaining mappings, expanding protocol and configuration support, improving performance, validating end-to-end behavior, and ensuring compatibility with the latest supported OpenTelemetry Semantic Conventions.

Todos

Note: This TODO list is not exhaustive and will be updated as Phase 2 progresses.

Mapping

• Required resource mapping chore(otlp-exporter): added missing resource mapping #2684
• FaaS resource mapping chore(otlp-exporter): added faas.name resource mapping #2688
• Runtime metrics mapping
• Complete metrics mapping
• Log mapping to the OTLP /v1/logs endpoint
• Events mapping (including detailed error, exception, and stack trace support)
• Fix HTTP request/response header mapping chore(http): captured request and response headers separately #2680
• Fix any misisng or incorrect mappings for otel semconv(latest)
• Make instrumentation scope name configurable instead of hardcoded

Protocol & Export

• Support the agent announcement cycle disablement use case
• Add support for additional OTLP protocols:
• OTLP/gRPC
• OTLP HTTP/protobuf
• Add serverless endpoint support
• Review batching limits (maximum spans per request, payload size restrictions)

Configuration

• Add extended exporter configuration options (endpoint, protocol, etc.)
• Validate configuration precedence with the new Node.js configuration model

Performance

• Parallelize span conversion in converter.js
• Perform performance testing and validation

Validation & Testing

• Validate end-to-end export behavior and infrastructure correlation

Public docs

• public doc update

Reference: https://jsw.ibm.com/browse/INSTA-99642
Tech spec: otlp-exporter