Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update eks-observe.md #766

Closed
wants to merge 2 commits into from
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion doc_source/eks-observe.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,8 @@ Monitoring is an important part of maintaining the reliability, availability, an
+ Who you do intend to perform the monitoring tasks?
+ Whom do you want notifications to be sent to when something goes wrong?

Note that one of the fallacies of distributed computing is that observability is optional. It's a prevalent but wrong assumption. To have a reliable and changeable system, you need to have proper observability in place.

## Logging and monitoring on Amazon EKS<a name="logging-monitoring"></a>

Amazon EKS provides built\-in tools for logging and monitoring\. Control plane logging records all API calls to your clusters, audit information capturing what users performed what actions to your clusters, and role\-based information\. For more information, see [Logging and monitoring on Amazon EKS](https://docs.aws.amazon.com/prescriptive-guidance/latest/implementing-logging-monitoring-cloudwatch/amazon-eks-logging-monitoring.html) in the *AWS Prescriptive Guidance*\.
Expand Down Expand Up @@ -56,4 +58,4 @@ Amazon Web Services provides various tools that you can use to monitor Amazon EK
| Applications | [Amazon DevOps Guru](https://aws.amazon.com/about-aws/whats-new/2021/11/amazon-devops-guru-coverage-amazon-eks-metrics-cluster/) | It detects node\-level operational performance and availability\. | [Setup procedure](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/deploy-container-insights-EKS.html) |
| Applications | [AWS X\-Ray](https://docs.aws.amazon.com/xray/latest/devguide/aws-xray.html) | It receives trace data about your application\. This trace data includes ingoing and outgoing requests and metadata about the requests\. For Amazon EKS, the implementation requires the OpenTelemetry add\-on\. | [Setup procedure](https://docs.aws.amazon.com/xray/latest/devguide/xray-instrumenting-your-app.html) |
| Applications | [Amazon CloudWatch Observability Operator](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/WhatIsCloudWatch.html) | The Amazon CloudWatch Observability Operator collects metrics, logs, and trace data\. It sends them to Amazon CloudWatch and AWS X\-Ray\. | [Setup procedure](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/install-CloudWatch-Observability-EKS-addon.html) |
| Control plane | [Prometheus](prometheus.md) | CloudWatch Logs ingestion, archive storage, and data scanning rates apply to enabled control plane logs\. | [Setup procedure](https://prometheus.io/) |
| Control plane | [Prometheus](prometheus.md) | CloudWatch Logs ingestion, archive storage, and data scanning rates apply to enabled control plane logs\. | [Setup procedure](https://prometheus.io/) |