felpasl opened a new pull request, #12696: URL: https://github.com/apache/apisix/pull/12696
### Description #### Introduced a comprehensive set of custom logging variables as functions, including: - latency: Total request latency in milliseconds - upstream_latency: Time spent communicating with upstream servers - apisix_latency: APISIX processing time (total latency minus upstream latency) client_ip: Remote client IP address - start_time: Request start time in milliseconds - hostname: Server hostname - version: APISIX version - request_method: HTTP method - request_headers: Request headers - request_querystring: Query parameters - request_body: Request body (with size limits) - response_status: HTTP response status - response_headers: Response headers - response_size: Response size in bytes - response_body: Response body - upstream: Upstream server address - url: Full request URL - consumer_username: Consumer username - service_id: Associated service ID - route_id: Associated route ID #### Simplified the function to use the custom_vars table for dynamic variable resolution, replacing hardcoded logic for request_body with a generic approach. #### Added group_id to the consumer object in full log entries. #### Which issue(s) this PR fixes: <!-- *Automatically closes linked issue when PR is merged. Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`. --> Fixes # ### Checklist - [ ] I have explained the need for this PR and the problem it solves - [ ] I have explained the changes or the new features added to this PR - [ ] I have added tests corresponding to this change - [ ] I have updated the documentation to reflect this change - [ ] I have verified that this change is backward compatible (If not, please discuss on the [APISIX mailing list](https://github.com/apache/apisix/tree/master#community) first) <!-- Note 1. Mark the PR as draft until it's ready to be reviewed. 2. Always add/update tests for any changes unless you have a good reason. 3. Always update the documentation to reflect the changes made in the PR. 4. Make a new commit to resolve conversations instead of `push -f`. 5. To resolve merge conflicts, merge master instead of rebasing. 6. Use "request review" to notify the reviewer after making changes. 7. Only a reviewer can mark a conversation as resolved. --> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
