Logs are an important part of tracking and debugging issues which are occurring throughout your system. Every process or service produces logs, and Burris Builder provides several ways of accessing those logs, which are covered here.
Burris Builder Access
For every site you build with Burris Builder Admin, logs are available inside the website management panel. Select the site from your homepage and there are two options for both access and error logs. Clicking on the location of the logs will present tail of the logs for access to the latest messages. You may also download the entire log by selecting the Download log messages option.
Web Server: Nginx and PHP-FPM
Nginx and PHP-FPM generate their own messages, but Burris Builder makes some standardized adjustments to combine messages into a single log file for organization. Further, adjustments are made to logging according to location, and website type. Nginx is set not to log access to basic assets, for instance, and dev sites report more verbose debugging information -and report more errors to the screen- than a live site which is set to only report critical errors and hides error messages from the screen. Details of these options are below.
Adjusting Nginx Logs
Reading RDS log files directly into the Burris Builder Admin is an active development.
Logs for your RDS database are generated and stored in your AWS console. From your dashboard, select RDS. Then click "Instances" from the left column and select the instance from which you would like to retrieve. Along the bottom, a "Logs" button is available. Clicking this button will reveal the most recent events, as well as a series of your latest logs, if any.
Burris Builder installs the AWS Logs service and a set of configuration files to send important log files to the console. This helps retrieve log files should the instance be stopped or even deleted. The Burris Builder instance must be assigned a role with proper permissions in order for CloudWatch Logs to work correctly.
From your AWS Console dashboard, click on "CloudWatch". On the left side panel, click "Logs". If your server was correctly setup with a role, you will see logs which correlate to the various logs available for your system. Note that empty logs will not generate a Log Group here. As soon as the log contain entries, it will show up in this panel.
Clicking on a log group will reveal the IP of the instances which delivered, followed by the instance ID. Both of these identifiers may be found under the Ec2 -> Instance dashboard once the instance has been selected under "Private DNS" and "Instance ID" respectively.
If you have started an stopped a number of instances, you may reduce the number of log entries by typing the IP or instance ID of the log titles.