Request router logs
Request router provides different log levels that can be changed after deployment. The following log levels are provided:
1 | trace |
2 | debug |
3 | info |
4 | warning\warn |
5 | error |
6 | critical |
By default, the log level is 1.
Steps to increase the request router log level:
- Execute the following command to log in to the primary pod:
kubectl exec -it -n <primary-server-namespace> <primary-pod-name> -- /bin/bash
- To set the request router log level, run the following command once in the primary server shell prompt:
vxlogcfg -a -p 51216 -o 527 -s DebugLevel=<log-level-value>
For example, to set the log level to critical, run the following command:
vxlogcfg -a -p 51216 -o 527 -s DebugLevel=6
Request router pod logs are collected by fluentbit collector pod.
The fluentbit collector writes request router logs to the log volume using the following directory convention:
/usr/openv/fluentbit/logs/<date>/<namespace>/<request-router-pod-name>/<container-name>/<log file>
To view request router logs, execute the following command to get a shell to the running fluentbit collector container:
kubectl exec -it -n <primary-server-namespace> <fluentbit-collector-pod-name> -- /bin/bash
Once in the fluentbit collector pod shell prompt, run the following command to view the list of logs:
ls /usr/openv/fluentbit/logs/<date>/<namespace>/<request-router-pod-name>/<container-name>/