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
Unsuppressed Pod metadata is still present in%kubernetes_logs. To avoid remap and additional resource consumption, it is better for it to work as described in the documentation.
Unsuppressed Pod metadata is still present in%kubernetes_logs. To avoid remap and additional resource consumption, it is better for it to work as described in the documentation.
Thanks for confirming! I agree it is a bug that should be fixed, just that remap could be a workaround for now.
A note for the community
Problem
I have the following configuration in the Vector agent:
However, the pod_annotation_fields are still present, and the suppression doesn’t work as expected according to the documentation: https://vector.dev/docs/reference/configuration/sources/kubernetes_logs/#node_annotation_fields
What is wrong with the configuration, and how can I suppress these fields?
Configuration
No response
Version
0.38.0-debian
Debug Output
No response
Example Data
No response
Additional Context
No response
References
No response
The text was updated successfully, but these errors were encountered: