obproxy.log records logs for detailed OceanBase Database Proxy (ODP) information. This file is the most comprehensive one.
Log format
The general format of logs in obproxy.log is as follows:
[time] log_level [module] file_name:line_number [thread_id][trace_id] [log_used_time] [dropped_msg_count] info
As shown above, a log usually consists of a header and a message.
Fields in the header are described as follows:
time: the time when the log was printed.log_level: the log level. Valid values from low to high are DEBUG, TRACE, WDIAG, EDIAG, INFO, WARN, and ERROR.module: the module name used for log printing.function: the function name used for log printing. The function name is displayed only for logs at theWARNorERRORlevel.file_name:line_number: the code source file name and line number used for log printing.thread_id: the thread ID used for log printing.trace_id: the trace ID of the task, which is unique at the task level. You can obtain all logs of a task based on its trace ID.log_used_time: the processing time of the previous log (including the time spent on writing the log to the file in asynchronous log scenarios).dropped_msg_count: dc=xx, where xx indicates the number of logs discarded between the current log and the previous log. If no logs are discarded, the value is 0.
The message usually describes the specific log content.
Examples
Here is an example of a log in obproxy.log:
[2024-01-05 14:15:51.538358] ERROR [PROXY] sig_direct_handler (ob_proxy_main.cpp:899) [14699][Y0-00007F65185CD4C0] [lt=0] [dc=0] receive signal(sig=15)
The log can be decomposed as follows:
time:
2024-01-05 14:15:51.538358log_level:
ERRORmodule:
PROXYfunction:
sig_direct_handlerfile_name:line_number:
ob_proxy_main.cpp:899thread_id:
14699trace_id:
Y0-00007F65185CD4C0log_used_time:
lt=0dropped_msg_count:
dc=0info:
receive signal(sig=15)