---
title: "Comment by Abhinav Sharma on \"Observability on Amazon EKS: Metrics, Logs and Traces\" | Hashnode"
description: "Following one controlled failure across all three signals is the part most observability tutorials skip. Tying metrics, logs and traces to the same incident is"
url: "https://hashnode.com/posts/observability-on-amazon-eks-metrics-logs-and-traces/6ad8fa2fbdabbdaedf98778d/comment/6ad90c5342d8717484079995"
---

[Discussion](https://hashnode.com/posts/observability-on-amazon-eks-metrics-logs-and-traces/6ad8fa2fbdabbdaedf98778d)

Comment [Observability on Amazon EKS: Metrics, Logs and Traces](https://hashnode.com/posts/observability-on-amazon-eks-metrics-logs-and-traces/6ad8fa2fbdabbdaedf98778d)

[Abhinav Sharma](https://hashnode.com/@abhinavs1920)

[Oct 21](https://hashnode.com/posts/observability-on-amazon-eks-metrics-logs-and-traces/6ad8fa2fbdabbdaedf98778d/comment/6ad90c5342d8717484079995)

Following one controlled failure across all three signals is the part most observability tutorials skip. Tying metrics, logs and traces to the same incident is what makes the stack useful instead of just installed.

[Ferhat Yildiz](https://hashnode.com/@turingts)

[Oct 21](https://hashnode.com/posts/observability-on-amazon-eks-metrics-logs-and-traces/6ad8fa2fbdabbdaedf98778d/comment/6ad90c5342d8717484079995#reply-6ad92422786cf66498f3e80f)

Thanks, Abhinav. That was the aim: make the connection between the signals tangible, rather than stop at deploying the tools.