Repository navigation
feat(telemetry): promote bounded native OTLP spans - #10
Merged
Merged
Conversation
feat(telemetry): export bounded native OTLP spans
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adds an optional native OTLP/HTTP tracer adapter to the shared telemetry SDK. It exports actual SDK spans with an explicit attribute projection, bounded admission, batching, retries and shutdown, and reports successful batches, failures, loss and last delivery time. Existing local output and its opt-out/security behavior remain available.
Verification: all-feature workspace tests and Clippy; actual TCP/protobuf export and retry checks; unavailable collector queue/loss acceptance; producer SDK checks, canonical projection checks, audit/license checks; real PostgreSQL, Vector and OpenObserve Compose acceptance including exporter opt-out, incidents and durable delivery.