Logs
Analyzing logs is an important part of maintaining a stable and secure website. Error logs often help to identify bugs and other issues. Here is how on fortrabbit.
Log usage is subject to change. For now an intermediate solution is offered. The output format and kind of access will change.
# Tailing logs
- Login by SSH to the environment
- Run
frbit-tail-logsto see live log streaming
This will provide you a stream of logs.
# Log files in your CMS or framework
Mind that your CMS or framework might pipe logs to a different location, other than stderr and stdout. If they do, you will not see the error output in the fortrabbit dashboard. You can still access the logs by SSH or SFTP, please see your CMS / framework docs where the logs are stored.
Most CMS and frameworks also offer options to send these logs to the standard locations. With the software template the setting is getting pre-populated, if possible, by ENV var.
# Verbose logging
Your CMS / framework might offer verbose logging, often this is connected to environment settings of the CMS / framework. Often more debugging information is printed with the error and sometimes errors are even send to the browser. Use that with care, since it can have a considerable performance impact. The general advice is to use it for development and staging environments, but not for production. If you happen to have an issue in production that requires verbose logging, turn it off, after you have finished.
Found a tpyo?Edit