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
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
By default when we installed adot operator on an EKS cluster via helm chart, only basic metrics are generating and pushed to AWS Cloudwatch. Few metrics such as 'node_status_condition_ready` , 'pod_container_status_running' and few more which fall under aws enhanced observability metrics are not populated
Describe the solution you'd like
A clear and concise description of what you want to happen.
We need an way to enabled "enhanced observability" while deploying adot. As of now adot is collecting only basic metrics. If we go with cloudwatch agents, there is an option to enabled "enhanced observability" which is collecting required metrics for EKS cluster whereas when deploying adot, we dont see some metrics
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
For now, the alternate solution is to use native aws cloudwatch with "enhanced observability" to have the EKS metrics such as 'node_status_condition_ready` and 'pod_container_status_running'
Additional context
Add any other context or screenshots about the feature request here.
If you install using AWS Distro for OpenTelemetry, you install Container Insights but do not get Container Insights with enhanced observability for Amazon EKS. You will not collect the detailed metrics supported in Container Insights with enhanced observability for Amazon EKS.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
By default when we installed adot operator on an EKS cluster via helm chart, only basic metrics are generating and pushed to AWS Cloudwatch. Few metrics such as 'node_status_condition_ready` , 'pod_container_status_running' and few more which fall under aws enhanced observability metrics are not populated
Describe the solution you'd like
A clear and concise description of what you want to happen.
We need an way to enabled "enhanced observability" while deploying adot. As of now adot is collecting only basic metrics. If we go with cloudwatch agents, there is an option to enabled "enhanced observability" which is collecting required metrics for EKS cluster whereas when deploying adot, we dont see some metrics
below page has detail with metrics which are available only in "enhanced observability"
https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Container-Insights-metrics-EKS.html
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
For now, the alternate solution is to use native aws cloudwatch with "enhanced observability" to have the EKS metrics such as 'node_status_condition_ready` and 'pod_container_status_running'
Additional context
Add any other context or screenshots about the feature request here.
Reference:
https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Container-Insights-EKS-otel.html
If you install using AWS Distro for OpenTelemetry, you install Container Insights but do not get Container Insights with enhanced observability for Amazon EKS. You will not collect the detailed metrics supported in Container Insights with enhanced observability for Amazon EKS.
The text was updated successfully, but these errors were encountered: