Aias00 opened a new issue, #10672:
URL: https://github.com/apache/rocketmq/issues/10672
### Before Creating the Bug Report
- [x] I found a bug, not just asking a question, which should be created in
GitHub Discussions.
- [x] I have searched the existing issues and believe that this is not a
duplicate.
- [x] I have confirmed that this bug belongs to the current repository, not
other repositories of RocketMQ.
### Runtime platform environment
All platforms running RocketMQ Proxy with gRPC clients.
### RocketMQ version
develop branch
### JDK Version
All supported JDK versions
### Describe the Bug
logs the full when the telemetry observer is missing or when fails.
Some telemetry commands can contain user message data or large diagnostic
payloads. For example:
- carries a message when Proxy asks a client to consume a message directly.
- carries a message for transaction recovery.
- Other telemetry commands may also carry verbose diagnostics.
When a client disconnects or the telemetry stream is already completed, this
failure path can write the complete protobuf command into Proxy logs. That
makes troubleshooting noisier and may expose message payloads in operational
logs.
Relevant code:
### Steps to Reproduce
1. Create a gRPC client channel in Proxy.
2. Send a telemetry command that carries a message payload, such as .
3. Make the telemetry observer missing or closed before writes the command.
4. Observe Proxy logs.
### What Did You Expect to See?
Proxy should log a compact command summary, such as command type and
channel/client ID, without serializing the full protobuf payload.
### What Did You See Instead?
Proxy logs the full , which can include message content and make runtime
diagnostics noisy or sensitive.
### Additional Context
This is related to Proxy-side gRPC client runtime diagnostics. The fix
should be additive and local to logging: replace full command logging with a
sanitized command summary while preserving enough context to debug telemetry
write failures.
--
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]
