Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Self instumentation config mismatch for "api_key" and "secret_token" in libbeat instrumentation #13690

Closed
1pkg opened this issue Jul 12, 2024 · 0 comments
Assignees
Labels
Milestone

Comments

@1pkg
Copy link
Member

1pkg commented Jul 12, 2024

This is a followup issue discovered after #13597. When APM Server is self-instrumented in the managed mode some of the APMConfig ("api_key" and "secret_token") sent by Elastic Agent are getting ignored because of the additional marshaling that erase original config keys here.

This will break self-instrumentation setup when "api_key" or "secret_token" authentication is configured. Therefore we should fix the mismatched config propagation to libbeat instrumentation and make sure that the authentication works as expected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant