Summary
The Microsoft Agent Framework's _chat_message_store.py creates a GlideClient without setting a client_name. This means connections appear anonymous in monitoring tools like CLIENT LIST and Valkey Admin.
Suggested Fix
In python/packages/valkey/agent_framework_valkey/_chat_message_store.py (line ~67), add client_name to the GlideClientConfiguration:
cfg = GlideClientConfiguration(
[NodeAddress(host, port)],
client_name="ms_agent_framework_chat_store_client",
)Why This Matters
When monitoring a Valkey server with multiple connected applications, CLIENT LIST shows each connection's name. Without a client name, operators cannot distinguish Microsoft Agent Framework connections from other anonymous clients. This is especially important in production environments with ElastiCache where multiple services share the same Valkey cluster.
Setting client_name sends a CLIENT SETNAME command on connection, making the connection identifiable in:
CLIENT LIST output- Monitoring dashboards (e.g., Valkey Admin)
- CloudWatch metrics (ElastiCache)
Naming Convention
Suggested client name: ms_agent_framework_chat_store_client
Pattern: {project}_{purpose}_client
ms_agent_framework = project namechat_store = purpose (chat message persistence)_client = convention (matches Valkey Admin naming pattern)
Summary
The Microsoft Agent Framework's
_chat_message_store.pycreates aGlideClientwithout setting aclient_name. This means connections appear anonymous in monitoring tools likeCLIENT LISTand Valkey Admin.Suggested Fix
In
python/packages/valkey/agent_framework_valkey/_chat_message_store.py(line ~67), addclient_nameto theGlideClientConfiguration:Why This Matters
When monitoring a Valkey server with multiple connected applications,
CLIENT LISTshows each connection's name. Without a client name, operators cannot distinguish Microsoft Agent Framework connections from other anonymous clients. This is especially important in production environments with ElastiCache where multiple services share the same Valkey cluster.Setting
client_namesends aCLIENT SETNAMEcommand on connection, making the connection identifiable in:CLIENT LISToutputNaming Convention
Suggested client name:
ms_agent_framework_chat_store_clientPattern:
{project}_{purpose}_clientms_agent_framework= project namechat_store= purpose (chat message persistence)_client= convention (matches Valkey Admin naming pattern)