Hi, The current Apache APISIX's 'access.log' format is as follows: 9.35.159.205 - - [20/Apr/2020:16:46:39 +0800] service-61ge01ri-1251890925.szjr.apigw.tencentcs.com:9080 "GET /e H7.29.0" - 0.000
Generally speaking, it contains less information. At present, the 'access.log' of our gateway usually has the following fields, more fields can more easily locate the problem: [route_id:$route_id][service_id:$service_id][consumer_id:$consumer_id][upstream_id:$upstream_id][host:$host][/release/m1_vivo_formal_1][https][rsp_st:200][ups_st:200][cip:39.65.54.127][uip:9.18.52.5:7999 ][vip:111.231.179.251][rsp_len:570][req_len:422][req_t:0.039][ups_rsp_t:0.039][ups_conn_t:0.003][ups_head_t:0.039][err_msg:-][tcp_rtt:39000][162780][20/Apr/2020:18:41:14 +0800][req_id:cf7c3ed06065bfac123448c67745c019] I hope to optimize the 'access.log' in version 1.3 yousa, Ming Wen <wenm...@apache.org> 于2020年4月21日周二 下午3:58写道： > Hi, community, > Version 1.2 has been released and it's time to discuss version 1.3. > > After the 1.2 release, Apache APISIX fixed several security issues, > and I recommend that we start the 1.3 release as soon as possible, > mainly fixing security issues, and performance optimization of the > Prometheus plugin. > > What do you think? > > Thanks, > Ming Wen, Apache APISIX & Apache SkyWalking > Twitter: _WenMing >
