Best Practices for Observability on AWS

0
2
Asked By CuriousCoder123 On

I've been diving into observability concepts like metrics, logs, and traces specifically for AWS. From my research, it seems that AWS mainly relies on CloudWatch for observability along with X-Ray for tracing, though X-Ray is integrated into CloudWatch. I want to maintain my observability in OTEL format, so I'm considering using the ADOT collector to push metrics from Prometheus/OTEL SDK, collect logs from containers, and send traces to CloudWatch. This means I would need to set up log groups, metric streams, and configurations for X-Ray. Is this approach advisable?

3 Answers

Answered By InfoSeeker88 On

Your setup sounds reasonable. You can definitely send OTEL data to CloudWatch. You'll need to create log groups and configure permissions for shipping your metrics. CloudWatch has Log Insights for log queries, which is decent, but not the best. It should work for your needs, though! What types of logs are you aiming to capture?

Answered By CloudNinja42 On

Yeah, you're on the right track! CloudWatch now has native support for OTEL, which is exciting because it makes integrating metrics, logs, and traces a lot smoother. Just check out the launch announcement if you haven’t already! It's a solid option for observability on AWS.

Answered By DataWhiz321 On

Just keep in mind that CloudWatch can get really pricey, especially with data storage and if you're streaming data to third-party services. If you're using OTEL, have you considered streaming to your own Prometheus instance instead? That could help save some costs!

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.