1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
Few things to validate.
- Can the containers reach the Amazon CloudWatch endpoint. For example, monitoring.us-west-1.amazonaws.com - this could be via the internet - eg a NAT gateway or via a VPC endpoint. basically your containers or the host need to be able to reach that endpoint to publish to CloudWatch
- Has the host got the right permissions to write to CloudWatch - you can confirm this by checking CloudTrail for access denied errors
- Are there any errors in the logs for the agent on the container regarding publishing of telemetry
con risposta un anno fa
Contenuto pertinente
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 9 mesi fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 2 anni fa
I am able to see performance log and metrics published to cloudwatch. There is no errors in logs for the agent. In cloudwatch->container insights -> performance monitoring, the drop down menu "select cluster" is empty. I suspect it might work for ecs fargate, but not eks fargate