Aias00 opened a new issue, #10676:
URL: https://github.com/apache/rocketmq/issues/10676
### Before Creating the Bug Report
- [x] I have searched the existing issues and pull requests.
### Runtime platform environment
All platforms.
### RocketMQ version
develop branch.
### JDK Version
Not applicable.
### Describe the Bug
`ClientActivity.processTelemetryException` logs the full inbound gRPC
`TelemetryCommand` when processing a client telemetry request fails with an
internal error:
```java
log.warn("process client telemetryCommand failed. request:{}", request, t);
```
Client telemetry requests can include nested protobuf messages and runtime
metadata. Logging the full protobuf request can expose more client-side
telemetry data than needed for diagnosis and can also produce very large
warning logs.
This is separate from #10672, which covers outbound telemetry write failures
in `GrpcClientChannel`. This issue covers inbound telemetry request processing
failures in `ClientActivity`.
### Steps to Reproduce
1. Send a gRPC telemetry request that triggers an internal exception in
`ClientActivity.telemetry` processing.
2. Observe the warning log emitted by `processTelemetryException`.
3. The current log serializes the complete `TelemetryCommand` request.
### What Did You Expect to See?
The warning log should keep useful diagnostic fields, such as command type,
status code, nonce, client type, and pub/sub case, without logging the complete
protobuf request.
### What Did You See Instead?
The warning log prints the full `TelemetryCommand` object as `request:{}`.
### Additional Context
This is a small Proxy gRPC diagnostics hardening issue. It aligns with the
Proxy Admin / runtime diagnostics track by making telemetry error logs safe and
bounded while preserving enough context for troubleshooting.
--
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]
