[Bug] Proxy gRPC telemetry exception logs full client TelemetryCommand

[Aias00]

Before Creating the Bug Report

• 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:

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.

[RockteMQ-AI]

Issue Evaluation

Category: type/bug | Status: Confirmed

The full-TelemetryCommand logging in ClientActivity.processTelemetryException has been verified against the current develop branch.

Root Cause: ClientActivity.java:362 — log.warn("process client telemetryCommand failed. request:{}", request, t) serializes the complete inbound TelemetryCommand protobuf when an internal processing error occurs.

Impact: Warning logs can become excessively large and may expose client-side telemetry metadata beyond what is needed for diagnosis.

Severity: Low — diagnostics quality issue, no functional impact.

Suggested fix: Replace full request logging with a compact summary (command type, status code, nonce, client type, pub/sub case) while preserving debuggability.

An automated fix proposal will be generated. Reply /approve to proceed with PR generation.

---

Automated evaluation by github-manager-bot