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
As we roll out the architecture change to beats receivers there will be cases where configuration translation is only possible for a subset of all configurations. A current example would be Kerberos authentication in the Elasticsearch output being an unsupported translation.
In these cases we expect a standard error to be returned from the translation methods that allow agent to automatically fall back to the current runtime implementation.
The primary use case for this is eagerly migrating use case to beats receivers by defaulting the feature flag to true, in which we will want to fall back in some known cases with limitations.
As an optimization for user experience, when the feature flag defaults off but is set to true manually we should not silently fall back for either fail immediately or ensure that the affected components are marked as failed in the agent status report.