Open wklken opened 9 months ago
looks like you will probably have to patch apisix... but let me find something.
looks like you will probably have to patch apisix... but let me find something.
thanks @shreemaan-abhishek
We are facing difficulties because the error.log format cannot be customized to include a request_id, and the response body lacks useful information. Consequently, we have to manually query the logs, matching the date and URI to correlate error.log with access.log, for the developers.
looks like you will probably have to patch apisix... but let me find something.
thanks @shreemaan-abhishek
We are facing difficulties because the error.log format cannot be customized to include a request_id, and the response body lacks useful information. Consequently, we have to manually query the logs, matching the date and URI to correlate error.log with access.log, for the developers.
seems like the logger plugin will help u, u can see the http logger or file logger(may better)
there are no apisix variables or nginx variables represent the error message
for logger; and we can't add a customized field like request_id
into the error log format(https://github.com/apache/apisix/issues/9498), so can't link the access log record with the error log record.
there are no apisix variables or nginx variables represent the
error message
for logger; and we can't add a customized field likerequest_id
into the error log format(#9498), so can't link the access log record with the error log record.
ok i got it, looks like the plugin cant implement it for now, but i think its a good feat if we can get them from plugin
Description
the
error.log
the response body
I want to write a plugin to wrap the 502, and put the error message
upstream prematurely closed connection while reading response header from upstream
into the response bodyis there any way to retrieve the error message of nginx from lua?
Environment
apisix version
): 3.2.1uname -a
):openresty -V
ornginx -V
):curl http://127.0.0.1:9090/v1/server_info
):luarocks --version
):