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
However, now in the datadog logs UI, I have those values in two places. Once as a tag called container_name, and once as a facet called @kubernetes.container_name. This causes some confusion among users of the logs UI, on which one they should use.
Describe what you'd like to see:
I'd like an option like delete_tag_attributes. Where if it's set, and a tag is created for the log entry, it deletes the value from the record itself. Then I'd only see the tag in the logs UI, rather than two copies of the same information.
The option should default to false, to preserve existing behavior.
I could probably configure Datadog's log pipelines to strip out the extra attribute on the server, but it would be nice to avoid duplicating data sent to the server.
jszwedko
changed the title
Request: option to delete docker/kubernetes attributes that are also tags
Add an option to delete docker/kubernetes attributes that are also tags
Apr 23, 2024
Describe what happened:
The plugin helpfully adds tags like
image_name
andcontainer_name
to log entries, as described in the docs and in this source code.fluent-plugin-datadog/lib/fluent/plugin/out_datadog.rb
Lines 380 to 412 in 01f90b0
However, now in the datadog logs UI, I have those values in two places. Once as a tag called
container_name
, and once as a facet called@kubernetes.container_name
. This causes some confusion among users of the logs UI, on which one they should use.Describe what you'd like to see:
I'd like an option like
delete_tag_attributes
. Where if it's set, and a tag is created for the log entry, it deletes the value from the record itself. Then I'd only see the tag in the logs UI, rather than two copies of the same information.The option should default to false, to preserve existing behavior.
I could probably configure Datadog's log pipelines to strip out the extra attribute on the server, but it would be nice to avoid duplicating data sent to the server.
Steps to reproduce the issue:
n/a
Additional environment details (Operating System, Cloud provider, etc):
Fluentd 1.6.3, running on a Kubernetes cluster, version 1.18.6
The text was updated successfully, but these errors were encountered: