How should the developer gather more information about the application performance issues?
Configure the Amazon CloudWatch agent to push logs to Amazon CloudWatch Logs by using port 443.
Configure the Elastic Beanstalk .ebextensions directory to track the memory usage of the instances.
Configure the Amazon CloudWatch agent to track the memory usage of the instances.
Configure an Amazon CloudWatch dashboard to track the memory usage of the instances.
Explanations:
Configuring the CloudWatch agent to push logs to CloudWatch Logs using port 443 does not address the need to specifically track memory usage. While it allows for log aggregation, it does not provide direct insights into memory performance metrics.
Configuring the Elastic Beanstalk .ebextensions directory may allow for some customization, but it does not inherently provide a mechanism for tracking memory usage. It is more about deployment configurations rather than performance metrics.
Configuring the Amazon CloudWatch agent to track memory usage of the instances directly addresses the developer’s concern. The CloudWatch agent can collect and send detailed system-level metrics, including memory usage, which would help diagnose performance issues effectively.
While configuring a CloudWatch dashboard would allow visualization of memory usage, it does not gather data itself. The data needs to be collected first, which is the primary concern here. Therefore, it’s not the first step to resolving the performance issues.
I chart that the answer is:
Configure the Amazon CloudWatch agent to track the memory usage of the instances.