You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add CLIENT INFO command support to the Valkey GLIDE C# client. The CLIENT INFO command returns information and statistics about the current client connection in a human-readable format. It is supported by Valkey GLIDE core (request type ClientInfo) but is not yet implemented in the C# client.
Unlike CLIENT LIST (which returns info for all connected clients), CLIENT INFO returns info only for the current connection. The output format is the same single-line format used by CLIENT LIST, so the existing ClientInfo parsing type (introduced for CLIENT LIST in #277) can be reused.
Use Case
Users need to inspect the current connection's metadata (e.g., client ID, name, flags, database, subscriptions, connection age) for diagnostics, monitoring, and debugging purposes — without requiring the overhead or permissions of listing all clients.
Proposed Solution
Add GLIDE-native CLIENT INFO methods to the client interfaces (IBaseClient, IClusterClient) and implement in GlideClient and GlideClusterClient. Refer to the other Valkey GLIDE clients (Java, Python, Go, Node) for signature conventions and return types.
Describe the feature
Add
CLIENT INFOcommand support to the Valkey GLIDE C# client. TheCLIENT INFOcommand returns information and statistics about the current client connection in a human-readable format. It is supported by Valkey GLIDE core (request typeClientInfo) but is not yet implemented in the C# client.Unlike
CLIENT LIST(which returns info for all connected clients),CLIENT INFOreturns info only for the current connection. The output format is the same single-line format used byCLIENT LIST, so the existingClientInfoparsing type (introduced forCLIENT LISTin #277) can be reused.Use Case
Users need to inspect the current connection's metadata (e.g., client ID, name, flags, database, subscriptions, connection age) for diagnostics, monitoring, and debugging purposes — without requiring the overhead or permissions of listing all clients.
Proposed Solution
CLIENT INFOmethods to the client interfaces (IBaseClient,IClusterClient) and implement inGlideClientandGlideClusterClient. Refer to the other Valkey GLIDE clients (Java, Python, Go, Node) for signature conventions and return types.ClientInfotype introduced forCLIENT LIST(feat: AddCLIENT LISTcommand support #277) to parse the response.CLIENT INFOmethod onIServer(unlikeCLIENT LIST, which it does support).Acknowledgements
Related
CLIENT LISTcommand support #277 —CLIENT LISTcommand support (introduces theClientInfotype that can be reused).Additional Information
CLIENT INFOwas introduced in Redis 6.2 / Valkey 7.2.CLIENT LIST.ClientInfo = 306.