tju-yxq opened a new issue, #3291:
URL: https://github.com/apache/rocketmq-dashboard/issues/3291
## Problem
The Client Connections page always asks the backend for every connection:
```ts
void listConnections({ namesrvAddr: selectedEndpoint })
```
The backend endpoint already supports two filters:
```java
@RequestParam(required = false) String clusterId,
@RequestParam(required = false) String type
```
The frontend ignores both. It loads the full client inventory, then filters
locally by cluster and table column filters. On a large cluster this makes the
page slower than necessary and transfers rows the user has already excluded.
The page-level cluster selector can only filter after all producer and
consumer connections have been collected.
## Expected behavior
- Send the selected cluster filter to `/api/clients`.
- Send the selected client type filter to `/api/clients`.
- Keep local diagnostics and export based on the returned filtered set.
- Reset to the first page when filters change.
- Preserve existing request ownership and error behavior.
- Avoid sending a redundant request when only local column filters change.
## Why this matters
Client inventories can be large. Operators often inspect one cluster or one
client type while diagnosing a connection problem. Filtering at the backend
reduces response size and avoids paying for a full client scan when only a
subset is needed.
--
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]
