janiussyafiq opened a new pull request, #13187:
URL: https://github.com/apache/apisix/pull/13187
### Description
Clarifies the behavior of `logging.summaries` and `logging.payloads` in the
`ai-proxy` and `ai-proxy-multi` plugin documentation.
Previously, the documentation described these options ambiguously as "logs
request/response ...", which implied they controlled all forms of logging
including `error.log`. This caused confusion for users who expected setting
them to `false` to suppress all AI request-related log output.
The two options exclusively control whether LLM data is appended to
**structured access log entries** consumed by logging plugins (e.g.
`http-logger`, `kafka-logger`). They have no effect on debug messages written
to `error.log`.
#### 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 https://github.com/apache/apisix/issues/13118#issuecomment-4131466692
- number 2
### Checklist
- [x] I have explained the need for this PR and the problem it solves
- [x] I have explained the changes or the new features added to this PR
- [ ] I have added tests corresponding to this change
- [x] I have updated the documentation to reflect this change
- [x] 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)
No tests needed here since it's a pure documentation fix.
<!--
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]
