> For the complete documentation index, see [llms.txt](https://karansingh.gitbook.io/tutorialsdojo-wrong-answers-aws-sec-spec/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://karansingh.gitbook.io/tutorialsdojo-wrong-answers-aws-sec-spec/logging-and-monitoring-68/troubleshooting-elastic-beanstalk-logs.md).

# Troubleshooting Elastic Beanstalk Logs

* **With CloudWatch Logs, each instance in your Elastic Beanstalk environment streams logs to log groups** that you can configure to be retained for weeks or years, even after your environment is terminated that help you to **troubleshoot issues with your application or configuration files**.

* The **set of logs streamed varies per environment, but always includes `eb-activity.log` and access logs from the NGINX or Apache proxy server** that runs in front of your application.<br>

* If the **CloudWatch Logs Agent (awslogs) stopped pushing the log data to CloudWatch Logs, you can do the following:**
  * If logs **stopped pushing after a log rotation, check the supported log rotation methods**.<br>
  * If logs are only **pushed for a short time after the awslogs agent is restarted, check for duplicates in the \[logstream] section of the agent configuration file**. Each section must have a unique name.<br>
  * If the **awslogs.log log file takes up too much disk space, check the log file for errors and correct them**.<br>
  * If the log file only **contains informational messages, specify a lower logging level for the logging\_config\_file option** in the agent configuration file.