---
title: "Comment by Fabio Sarmento on \"Lessons Learned from Running Serverless Applications in Production on AWS\" | Hashnode"
description: "ngl, I totally relate to the struggles you mentioned with logging and tracing in serverless. We faced a similar situation where the complexity of distributed lo"
url: "https://hashnode.com/posts/lessons-learned-from-running-serverless-applications-in-production-on-aws/67fe329f647f06e151034e8b/comment/69b6a668d6abc7497bc46b1f"
---

[Discussion](https://hashnode.com/posts/lessons-learned-from-running-serverless-applications-in-production-on-aws/67fe329f647f06e151034e8b)

Comment [Lessons Learned from Running Serverless Applications in Production on AWS](https://hashnode.com/posts/lessons-learned-from-running-serverless-applications-in-production-on-aws/67fe329f647f06e151034e8b)

[Fabio Sarmento](https://hashnode.com/@sarmento)

[Mar 15](https://hashnode.com/posts/lessons-learned-from-running-serverless-applications-in-production-on-aws/67fe329f647f06e151034e8b/comment/69b6a668d6abc7497bc46b1f)

ngl, I totally relate to the struggles you mentioned with logging and tracing in serverless. We faced a similar situation where the complexity of distributed logs made it a nightmare to debug. Using structured logging really helped us too! Curious if you found any specific tools that worked best for alerting on business metrics?