feat(opentelemetry): expose OtlpExporter as public API #5855
+146
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Exposes the internal OTLP exporter as
OtlpExporter.make()to allow building custom multi-endpoint tracers or composing multiple exporters without copying internal code.Motivation
When building applications that need to send traces to multiple backends (e.g., Honeycomb + Axiom + Sentry), the current options are:
NodeSdkwith multipleSpanProcessors (requires@opentelemetry/sdk-trace-base)Exposing the exporter allows Effect-native multi-endpoint tracing without any OpenTelemetry SDK dependencies:
Changes
src/OtlpExporter.ts- public module re-exporting the internal exporter with proper JSDoc documentationsrc/index.ts- addedOtlpExporterexportTest Plan
🤖 Generated with Claude Code