Problem
HeartbeatSyncer logs full heartbeat sync data and subscription sets in several failure/debug paths:
sync register heart beat. topic:{}, data:{}heartbeat register broadcast failed ... subList:{}heartbeat submit register broadcast failed ... subList:{}start process remote channel. data:{}, clientChannelInfo:{}heartbeat consume message failed. msg:{}, data:{}
The heartbeat data contains SubscriptionData, including subscription expressions. These logs are useful for diagnostics, but printing the full payload can expose business subscription details and creates large log lines under client churn.
Expected behavior
Proxy heartbeat sync logs should keep diagnostic fields such as heartbeat type, group, clientId, client metadata, channel data presence, subscription count, and topic names, without logging the full subscription expressions or raw system message body.
Scope
RocketMQ Proxy / gRPC client runtime diagnostics and safe logging, related to the Proxy Admin / client-management track.
Problem
HeartbeatSyncerlogs full heartbeat sync data and subscription sets in several failure/debug paths:sync register heart beat. topic:{}, data:{}heartbeat register broadcast failed ... subList:{}heartbeat submit register broadcast failed ... subList:{}start process remote channel. data:{}, clientChannelInfo:{}heartbeat consume message failed. msg:{}, data:{}The heartbeat data contains
SubscriptionData, including subscription expressions. These logs are useful for diagnostics, but printing the full payload can expose business subscription details and creates large log lines under client churn.Expected behavior
Proxy heartbeat sync logs should keep diagnostic fields such as heartbeat type, group, clientId, client metadata, channel data presence, subscription count, and topic names, without logging the full subscription expressions or raw system message body.
Scope
RocketMQ Proxy / gRPC client runtime diagnostics and safe logging, related to the Proxy Admin / client-management track.