![]() ![]() Then, compare the access logs with the application logs to identify the pattern of increased errors. For an increased number of 4xx and 5xx HTTP return codes, identify the cause of the increase by monitoring the access logs of the proxy server.Note: Operations that take longer than usual are typically environment deployments or configuration updates. ![]() Or, monitor the /var/log/eb-activity.log by logging in to your Amazon EC2 instance. For health check failures, see Basic health reporting, or see Enhanced health reporting and monitoring if you're using enhanced health reporting.įor operations that are taking too long, identify the operation in progress using the Elastic Beanstalk event stream.Troubleshoot the issue that caused the health warningīased on the health issues that you identify in the Enhanced Health Overview page, choose one of the following troubleshooting approaches: Now, you can view the overall health of your environment on the Enhanced Health Overview page.įor more information, see Enhanced health monitoring with the environment management console. In the navigation pane, choose Dashboard.In the Type column, look for recent events with a Severity type of WARN, and then note these events for troubleshooting later on.
0 Comments
Leave a Reply. |