Feature Request: Hope to support custom parameters for MonitorCmd

[Heachy]

Issue tracker is used for reporting bugs and discussing new features. Please use
stackoverflow for supporting issues.

Expected Behavior

It would be desirable to customize the monitor command instead of hard‑coding it as just MONITOR, since different cloud‑providers support different commands.

Current Behavior

func newMonitorCmd(ctx context.Context, ch chan string) *MonitorCmd { return &MonitorCmd{ baseCmd: baseCmd{ ctx: ctx, args: []interface{}{"monitor"}, }, ch: ch, status: monitorStatusIdle, mu: sync.Mutex{}, } }
It appears the command args are fixed to MONITOR, with no option to customize the monitor command.

Possible Solution

Expose setter for MonitorCmd args. My target command could be MONITOR followed by a node IP or ID, or an entirely different command. Direct configuration of the full command is required, instead of merely appending extra parameters.

Steps to Reproduce

Context (Environment)

Detailed Description

Possible Implementation

[ndyakov]

Hello @Heachy, can you provide some examples and documentation to the different cloud providers accepted arguments? In the official Redis documentation, the monitor command does not support arguments - https://redis.io/docs/latest/commands/monitor/ .

[Heachy]

Hi @ndyakov,

Thanks for raising this question.
As you pointed out, the native Redis MONITOR command does not take any arguments.
However, many cloud‑hosted Redis services implement custom extended commands for monitoring. Here are the examples I have collected:

1. Huawei Cloud:

• Cluster architecture: MONITOR ip:port
• Primary‑replica architecture: MONITOR

2. Tencent Cloud:

• Cluster architecture: IMONITOR nodeID
• Primary‑replica architecture: IMONITOR

I have not investigated Alibaba Cloud or AWS so far.
All of these custom commands return data in the identical streaming format as the original MONITOR command.

Therefore, I believe it would be reasonable to support configurable arguments for MonitorCmd.

[ndyakov]

@Heachy I haven't seen that, honestly. Can you point me to a documentation page? We do not support IMONITOR at all, and this case for ip:port. As far as I am concerned the append of an argument makes more sense than introducing a command that is not supported in Redis.