Aias00 opened a new issue, #7643: URL: https://github.com/apache/shenyu/issues/7643
## Goal Reduce avoidable diagnostic logging in request matching and large configuration synchronization. Suggested sequence: first implementation batch. ## Current evidence At the reviewed commit, `AbstractShenyuPlugin.defaultMatchSelector/defaultMatchRule` emits INFO success messages on the default matching path, independently of the explicit per-selector/per-rule success-log flags. Bootstrap disables matching-result caches by default. `ShenyuWebsocketClient.handleResult` logs the complete received payload at INFO. Existing Logback configurations already use async appenders; adding another async appender is not the objective. [Source at reviewed commit](https://github.com/apache/shenyu/blob/b4e115367fd57adc8aba332d655b1009932ba394/shenyu-plugin/shenyu-plugin-base/src/main/java/org/apache/shenyu/plugin/base/AbstractShenyuPlugin.java#L289) ## Scope and acceptance criteria - [ ] Gate routine match-success diagnostics behind DEBUG or the explicit matching-log setting; document the choice without duplicating messages. - [ ] Log configuration event metadata/count/size rather than full payloads at INFO; retain actionable failures and required audit records. - [ ] Regression tests cover disabled/enabled matching logs and unchanged routing results. - [ ] Compare fixed-load log bytes/sec, allocation rate, CPU and p99 before/after with identical logging destinations. - [ ] Report observed results and any diagnostic tradeoff. No performance improvement percentage is assumed before measurement. -- 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]
