Management logs
Management log detail levels, such as INFO, WARNING, and DEBUG, are configured in ase.conf.
Generated by controller and balancers, management logs are stored in the logs directory and include:
-
Controller logs –
controller.log -
Balancer log for port 80 (default port) –
balancer.log -
Balancer log for port 443 –
balancer_ssl.log
Controller logs
The controller.log file is a log file with data from the command-line interface (CLI), REST API, configurations, IPC, SSL, cluster, and ABS. Rotated every 24 hours, controller.log is the current file name. Older files are appended with a timestamp.
Balancer logs
The balancer.log file for port 80 and balancer_ssl.log file for port 443 are static files that are not rotated. These files contain information about IPC between controllers and balancer processes as well as IPC between balancer processes.
In a sideband ASE deployment, the balancer checks for request-response parsing error every 30 seconds. Parsing error statistics are logged in balancer.log file only if the balancer encounters parsing errors. If there are no errors in a 30-second period, the balancer.log file does not show the JSON output.
The following is a snippet of request-response parsing error statistics:
{
"sideband stats": {
"request parsing errors": {
"total requests failed": 1,
"request body absent": 0,
"request body malformed": 0,
"request source ip absent": 1,
"request source ip invalid": 0,
"request method absent": 0,
"request url absent": 0,
"request host header absent": 0,
"request authentication failure": 0,
"request error unknown": 0
},
"response parsing errors": {
"total responses failed": 1,
"response body absent": 0,
"response body malformed": 0,
"response code absent": 0,
"response authentication failure": 0,
"response correlation id not found": 1,
"response error unknown": 0
}
}
}The snippet shows that there was one parsing error for request and one for the response. The statistics also lists the type of request and response error.