Revise APM Instrumentation library injection details #33262
Merged
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.
Updated the section on instrumentation library injection to specify Single Step Instrumentation and added information on manual APM tracer library injection.
What does this PR do? What is the motivation?
Motivation: We recently received feedback from a customer that this documentation is confusing and does not highlight the "APM and DogStatsD" section will only result in environment variables being injected, and not tracing SDKs. The instrumentation section also uses an old URL which now redirects to the SSI documentation, and does not clearly state the difference between SSI and local SDK injection methods.
Changes made:
The PR aims clarify the different APM configuration methods by doing the following:
Merge readiness: