Which solution meets these requirements?
Run the Amazon CloudWatch agent in the existing EKS cluster. View the metrics and logs in the CloudWatch console.
Run AWS App Mesh in the existing EKS cluster. View the metrics and logs in the App Mesh console.
Configure AWS CloudTrail to capture data events. Query CloudTrail by using Amazon OpenSearch Service (Amazon Elasticsearch Service).
Configure Amazon CloudWatch Container Insights in the existing EKS cluster. View the metrics and logs in the CloudWatch console.
Explanations:
While running the Amazon CloudWatch agent in the EKS cluster can collect metrics and logs, it is not specifically designed for aggregating and summarizing container metrics in a centralized way. This option might require additional setup to ensure comprehensive logging and metric collection across all microservices.
AWS App Mesh is primarily a service mesh that provides application-level networking for microservices. It does not inherently collect or aggregate metrics and logs; rather, it helps with traffic management and service discovery. The logs and metrics would still need to be collected separately.
AWS CloudTrail captures account activity and API usage but is not designed for collecting application logs and metrics. It focuses on tracking changes and auditing actions rather than monitoring application performance. Using Amazon OpenSearch Service for querying CloudTrail data would not meet the requirements for centralized application log and metric aggregation.
Amazon CloudWatch Container Insights is specifically designed for monitoring and logging containerized applications running on Amazon EKS. It collects metrics and logs from the cluster and provides a centralized view in the CloudWatch console, making it the best solution for the company’s requirements.
I opine that the answer is:
Configure Amazon CloudWatch Container Insights in the existing EKS cluster. View the metrics and logs in the CloudWatch console.