- Newest
- Most votes
- Most comments
The issue you're experiencing with infinite loading in CloudWatch groups and the error message you're seeing could be related to a few different factors:
-
Browser-related issues: The error message you're seeing (awsc-head.js:2 [TangerineBox] Telemetry configuration is missing. Error: Error: Telemetry broker not found) suggests there might be a problem with how the AWS Console is loading in your browser. Try clearing your browser cache and cookies, or use a different browser to see if the issue persists.
-
Network connectivity: There could be network connectivity issues preventing the CloudWatch console from loading properly. This could be due to firewall settings, VPN configurations, or general internet connectivity problems.
-
AWS Console service issues: Occasionally, AWS may experience service issues that affect the console. Check the AWS Service Health Dashboard to see if there are any ongoing problems in your region, specifically with CloudWatch.
-
Permissions: Ensure that your IAM user or role has the necessary permissions to access CloudWatch and view log groups. Even if you think you have the right permissions, double-check your IAM policies.
-
Region selection: Make sure you're looking in the correct AWS region where your resources and log groups are located.
To troubleshoot:
- Try accessing other AWS services in the console to see if the issue is specific to CloudWatch.
- Test your connectivity to the CloudWatch endpoint using network diagnostic tools.
- If possible, try accessing the AWS console from a different network to rule out local network issues.
- If the problem persists after trying these steps, it may be best to contact AWS support for further assistance, as there could be an underlying account-specific issue.
Remember, if you need to view logs urgently while troubleshooting this console issue, you can use the AWS CLI or SDKs as an alternative method to access CloudWatch logs.
Sources
EC2: basic monitoring unavailable (load failed) | AWS re:Post
Log Groups not found | AWS re:Post
Relevant content
- asked a month ago