GitHub user chakravarthyBatna added a comment to the discussion: How to use mqadmin observer consumer client's status when consumer connect with Proxy
It depends on how your Proxy is deployed. - **Local mode** (Proxy runs inside the broker): gRPC consumers are registered in the broker, so `mqadmin` works as usual. - **Cluster mode** (separate Proxy): gRPC consumers are registered **only in the Proxy**. The Proxies share them with each other, but they are never sent to the brokers. `mqadmin consumerConnection -g <group>` asks a broker, so it says the group is not online. **What you can do in cluster mode:** 1. **Connections:** point `mqadmin` at the Proxy's **remoting** port (default `8080`, not the gRPC port `8081`). The Proxy answers this request from its own consumer table: ```bash sh mqadmin consumerConnection -n <namesrv> -g <group> -b <proxyHost>:8080 ``` 2. **Lag / progress:** `sh mqadmin consumerProgress -n <namesrv> -g <group>` (without `-s`) still works, because offsets and lag are read from the brokers. 3. **Limits:** `consumerProgress -s` and `consumerStatus` need detailed running info from each client. For gRPC clients the Proxy can only get a thread stack dump, so subscription and consume statistics are not available there. GitHub link: https://github.com/apache/rocketmq/discussions/11276#discussioncomment-18743744 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
