Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add TagFiltering Option with the DD Log Forwarder Parameters #791

Open
green2jello opened this issue May 21, 2024 · 3 comments
Open

Add TagFiltering Option with the DD Log Forwarder Parameters #791

green2jello opened this issue May 21, 2024 · 3 comments

Comments

@green2jello
Copy link

Describe what happened:
Currently when you set DdFetchLogGroupTags or DdFetchLambdaTags 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.

@sumedham
Copy link

sumedham commented Jun 4, 2024

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.

@billoneil
Copy link

@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.

@green2jello
Copy link
Author

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants