Skip to content

feat: add OTel adapter for OTLP ingestion#266

Draft
maximelb wants to merge 2 commits into
masterfrom
otel
Draft

feat: add OTel adapter for OTLP ingestion#266
maximelb wants to merge 2 commits into
masterfrom
otel

Conversation

@maximelb
Copy link
Copy Markdown
Contributor

@maximelb maximelb commented Mar 6, 2026

Summary

  • Adds a new otel adapter that acts as an OTLP endpoint for ingesting OpenTelemetry traces, metrics, and logs into LimaCharlie
  • Supports both gRPC and HTTP transports with protobuf and JSON content types
  • Each span/metric/log record is shipped individually as JsonPayload with resource and scope context, using event types otel_trace, otel_metric, otel_log
  • Uses the official go.opentelemetry.io/proto/otlp protobuf definitions for reliable, standards-compliant OTLP handling

Test plan

  • 31 tests covering conversion logic, config validation, gRPC integration, HTTP integration, error handling, and adapter lifecycle
  • Manual testing with an OTel SDK sending data to the adapter
  • Verify events appear correctly in LimaCharlie

🤖 Generated with Claude Code

maximelb and others added 2 commits March 6, 2026 08:50
Implements an OpenTelemetry adapter that acts as an OTLP endpoint,
accepting traces, metrics, and logs via both gRPC and HTTP (protobuf
and JSON). Each span/metric/log record is shipped individually as
JSON to LimaCharlie with resource and scope context preserved.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Ship the entire OTLP request as a single JSON event via protojson,
removing per-record conversion logic. This allows the backend
(legion_usp_proxy) to perform centralized mapping regardless of
how events arrive.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant