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
APM Server can be self-instrumented and when in managed mode, the configuration for the self-instrumentation contains more than what it's supported by the instrumentation package from libbeat, which APM Server currently rely on.
Missing configs are namely TLS and global labels.
This can potentially confuse users if they have specified such missing configs and it doesn't take place(missing global labels in traces, TLS config not applied in HTTP client etc.)
We should support all the configs that is sent by Elastic Agent, and for that we might want to consider having our implementation rather than making changes to libbeat to reduce our dependency on libbeat.
APM Server can be self-instrumented and when in managed mode, the configuration for the self-instrumentation contains more than what it's supported by the instrumentation package from libbeat, which APM Server currently rely on.
Missing configs are namely TLS and global labels.
This can potentially confuse users if they have specified such missing configs and it doesn't take place(missing global labels in traces, TLS config not applied in HTTP client etc.)
We should support all the configs that is sent by Elastic Agent, and for that we might want to consider having our implementation rather than making changes to libbeat to reduce our dependency on libbeat.
related ticket: #11381 (comment)
The text was updated successfully, but these errors were encountered: