[8.15] fix: Add wrapper around libbeat instrumentation to propagate missing tracer config (backport #13653) #13675
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.
Motivation/summary
This PR addresses the issue by adding a thin wrapper around libbeat instrumentation to propagate missing tracer config from elastic-agent via environmental variables.
Checklist
For functional changes, consider:
How to test these changes
Follow instructions in
Building an Elastic Agent container image with a locally built APM Server
andRunning an Elastic Agent container with a locally built APM Server
section inTESTING.md
, update the relevantagent.monitoring
sections inelastic-agent.yml
to see the config are propagated down to tracing correctly.Related issues
#13597
#11381
#13514
This is an automatic backport of pull request #13653 done by [Mergify](https://mergify.com).