Whether you're taking your first steps with Kubernetes or you're an experienced practitioner looking to sharpen your skills, our Amazon EKS workshop series delivers practical, real-world experience that moves you forward. Learn directly from AWS solutions architects and EKS specialists through hands-on sessions designed to build your confidence with Kubernetes. Register now and start building with Amazon EKS!
CloudWatch Application Insights Missing Load Balancer & API Gateway Components
Hello,
I am setting up CloudWatch Application Insights to monitor key services (excluding EC2 instances) across multiple production accounts. My goal is to include services like API Gateway, RDS DB Instance, ECS Cluster, EKS Cluster, and Load Balancer.
Steps I Took:
- Created a resource group in each production account using the OwnerTeam tag key to group resources.
- Created Application Insights using the resource group as the source. Issue: After setting up Application Insights and proceeding to the review step, I noticed that some Load Balancers and API Gateways are missing from the service components, even though they are included in the resource group.
Here the snapshot of the resource group:
Here the snapshot of the application insight component:
Has anyone encountered this issue before? Are there any additional configurations required to ensure all resources appear in Application Insights?
Thanks in advance!
- Newest
- Most votes
- Most comments
The issue you're experiencing with CloudWatch Application Insights not showing all your resources, particularly Load Balancers and API Gateways, is a known limitation of the service. Application Insights doesn't automatically include all resource types in its monitoring, even if they are part of the resource group you've specified.
For Load Balancers, it appears that Application Insights is only detecting one out of the five you have in your resource group. This partial detection could be due to various factors, such as the specific type of Load Balancer (ALB vs NLB) or how recently they were created.
Regarding API Gateways, these are currently not supported by CloudWatch Application Insights for automatic discovery and monitoring. This is why you're not seeing them in the Application Insights components, even though they're present in your resource group.
To address this issue:
-
For the missing Load Balancers, you may need to manually add them to your Application Insights monitoring. Check if there's an option to add components manually within the Application Insights configuration.
-
For API Gateways, since they're not currently supported by Application Insights, you'll need to set up separate CloudWatch alarms and dashboards to monitor these resources.
-
Ensure that all your resources have the necessary permissions and roles attached. For instance, make sure the AmazonSSMManagedInstanceCore and CloudWatchAgentServerPolicy policies are attached to the instance roles of your EC2 instances if you're using any.
-
If you're still missing resources that should be supported, it might be worth checking if there are any configuration issues or reaching out to AWS support for further assistance.
Remember that CloudWatch Application Insights is continually evolving, and AWS may add support for additional resource types in the future. In the meantime, for critical resources not showing up in Application Insights, you may need to use alternative methods for tracking and managing these resources, such as service-specific APIs, the AWS CLI, or other CloudWatch features.
Sources
AWS Resource Explorer does not see all Resources | AWS re:Post
Prerequisites to configure an application for monitoring - Amazon CloudWatch
Relevant content
- AWS OFFICIALUpdated 8 months ago
