You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: