You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When following this guide, no metrics are send to CloudWatch and the adot-collector is showing warnings.
Steps to reproduce
I followed the aforementioned guide.
Create EKS add-on with aws eks create-addon
I deployed the OpenTelemetryCollector custom resource.
What did you expect to see?
I expected that the official EKS add-on configures all necessary components to send metrics and logs to CloudWatch.
What did you see instead?
No metrics were sent to CloudWatch and the adot-collector showed warning.
Additional context
After some hours of online research, I analysed the kubernetes resources created by the adot-operator and discovered differences to the maintained helm charts.
I noticed, that the following resources were missing:
Service Accounts
Cluster Role
Cluster Role Binding
environment values
volumes
Moreover, I found out I needed to use eksctl to create a Service Account / IAM Role combination. I attached the following policy: arn:aws:iam::aws:policy/CloudWatchAgentServerPolicy.
Describe the bug
The EKS add-on documentation on the official AWS page is linking to this Getting Started Guide:
https://aws-otel.github.io/docs/getting-started/adot-eks-add-on
When following this guide, no metrics are send to CloudWatch and the adot-collector is showing warnings.
Steps to reproduce
I followed the aforementioned guide.
aws eks create-addon
OpenTelemetryCollector
custom resource.What did you expect to see?
I expected that the official EKS add-on configures all necessary components to send metrics and logs to CloudWatch.
What did you see instead?
No metrics were sent to CloudWatch and the
adot-collector
showed warning.Additional context
After some hours of online research, I analysed the kubernetes resources created by the
adot-operator
and discovered differences to the maintained helm charts.I noticed, that the following resources were missing:
Moreover, I found out I needed to use
eksctl
to create a Service Account / IAM Role combination. I attached the following policy:arn:aws:iam::aws:policy/CloudWatchAgentServerPolicy
.Eventually, I used the following manifest file:
The text was updated successfully, but these errors were encountered: