Open green2jello opened 4 months ago
Hi @green2jello, what's the underlying motivation for removing tags? Is it for ease-of-use and UX, or cost control purposes? Depending on that, we can look into finding a workaround or solution that works in this scenario.
@sumedham My use case for this feature would be cost control. Adding unneeded tags on all spans and logs adds up on the bytes ingested.
@sumedham . As mentioned by others, we would prefer not to send unneeded tags to Datadog, but we need said tags for AWS Billing and SCP purposes where resources are mandated to have tags for COST purposes, but not logging or metrics purposes.
Describe what happened: Currently when you set
DdFetchLogGroupTags
orDdFetchLambdaTags
this will send ALL AWS tags on the log group / AWS lambda as part of the message to datadog. We would like a similar option to the optional Log Filtering Parameters that provide a regex of tags that we explicitly include, or explicitly exclude.Describe what you expected: More control over which tags we send that are attached to resources. Tags for AWS that we use for cost analysis are not necessary to be sent with a whole log group and attached to each log message.