Add OTel profiling pipeline to collector config#16
Open
smith wants to merge 1 commit into
Open
Conversation
Routes profiling data from the OTLP receiver to Elasticsearch and debug exporters. The OTLP receiver already accepts profiling signals on ports 4317/4318. Closes #11 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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
1 participant
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
profiles/fromsdkpipeline to the OTel collector configurationotlp/fromsdkreceiver through toelasticsearch/otelanddebugexportersCloses #11
Test plan
docker compose up— verify otelcol starts without errorslocalhost:4317orlocalhost:4318and verify it reaches Elasticsearch🤖 Generated with Claude Code