---
title: "Discussion on \"Observability on Amazon EKS: Metrics, Logs and Traces\" | Hashnode"
description: "Discussion on \"Observability on Amazon EKS: Metrics, Logs and Traces\". Add OpenTelemetry, AMP, Fluent Bit and Grafana to an existing cluster—and follow a controlled failure across all three signals."
url: "https://hashnode.com/posts/observability-on-amazon-eks-metrics-logs-and-traces/6ad8fa2fbdabbdaedf98778d"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Observability on Amazon EKS: Metrics, Logs and Traces](https://blog.turingts.com/observability-on-amazon-eks-metrics-logs-and-traces?utm_source=hashnode&utm_medium=feed)

Add OpenTelemetry, AMP, Fluent Bit and Grafana to an existing cluster—and follow a controlled failure across all three signals.

Oct 21 · 27 min read · blog.turingts.com  
Read the article

-   [#aws](https://hashnode.com/tag/aws)
-   [#kubernetes](https://hashnode.com/tag/kubernetes)
-   [#opentelemetry](https://hashnode.com/tag/opentelemetry)
-   [#observability](https://hashnode.com/tag/observability)
-   [#terraform](https://hashnode.com/tag/terraform)
-   [#prometheus](https://hashnode.com/tag/prometheus)
-   [#grafana](https://hashnode.com/tag/grafana)

## Written by

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

@turingts · Amstelveen, Netherlands

  
[View profile](https://hashnode.com/@turingts)

Owner at Turing Technology Services

I’m a hands-on technology architect, engineer and founder of Turing Technology Services, with nearly two decades of experience in software engineering, platform engineering, site reliability engineering and cloud infrastructure. My work combines architecture and implementation with technical leadership, coaching and helping organisations adopt new engineering practices. I’ve worked with organisations including Shell, ING, ABN AMRO, Rabobank, Schiphol Group and Ahold Delhaize, across complex and regulated enterprise environments. On this blog, I share practical guides and perspectives on software architecture, cloud platforms, reliability and AI, explaining the reasoning behind technical choices as well as how to implement them.

## Responses 2

Comments are turned off for this post.

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