Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Feature Request: Apply Cloudwatch Log Group Tags as Datadog Tags
See original GitHub issueHello there!
We love the capabilities of the Data Logging Pipeline, and we use it quite heavily today! One feature we’ve always enjoyed is the nice UX of installing an agent and having it aggregate EC2 Tagging metadata as tags in Datadog’s Logging product.
We also make heavy use of the Datadog Log Forwader for our ECS Workloads, however, we’ve noticed that some of the metadata we used to get in EC2 isn’t necessarily working how we’d expect with Cloudwatch log groups.
What would be really nice is if this same behavior applied to Cloudwatch Log Groups so we wouldn’t have to encode aggregation data into our Structured Logs and try to parse it out via the Logging Pipeline.
For example, if we tag a Cloudwatch log group resource in AWS with
Env: 'production'
Service: 'auth'
We would love to have any logs from that log group be searchable and aggregated by those tags as well!
Issue Analytics
- State:
- Created 3 years ago
- Reactions:38
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Hello! We have a similar need. I added tags to the aws elasticsearch slow logs logroup but I am not able to see these tags in the the logs forwarded to datadog.
thank you!
Would love to see that 👍 we are forwarding API Gateway access logs to datadog using the lambda forwarder. Without the service and env tag it is hard to correlated these logs with the lambda invocations.