Repository navigation
Clarify declarative configuration support and profiling limits - #817
Merged
Merged
Conversation
shuwpan
approved these changes
Nov 4, 2026
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Fix the README's incorrect statement that the
distribution.splunkconfiguration block is unsupported. Document the supportedinstrumentations.http.trace_response_header_enabledoption, its default, and a YAML example that disables it.Clarify that setting
OTEL_CONFIG_FILEprevents the distribution from enabling continuous profiling, call graph profiling, and PostgreSQL trace correlation. Add the profiling limitation to the profiling guide as well.