Changes between Initial Version and Version 1 of Ticket #36879
- Timestamp:
- Jan 23, 2026, 8:44:35 AM (3 hours ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #36879 – Description
initial v1 3 3 == Context == 4 4 5 Redis documentation recommends that clients identify themselves via connection metadata to help operators monitor, debug, and reason about production systems (for example using ` `CLIENT SETINFO`` / ``CLIENT INFO``):5 Redis documentation recommends that clients identify themselves via connection metadata to help operators monitor, debug, and reason about production systems (for example using `CLIENT SETINFO` / `CLIENT INFO`): 6 6 7 7 https://redis.io/docs/latest/commands/client-setinfo/ … … 9 9 This information is intended to help Redis operators understand what software is connecting to their servers, especially in shared or multi-tenant environments. 10 10 11 Django’s Redis cache backend is built on top of ` `redis-py``, which means Redis connections created by Django are currently indistinguishable from other ``redis-py``-based clients in shared Redis deployments. This makes it harder for Redis operators to attribute traffic, diagnose issues, or understand cache usage patterns when multiple applications or frameworks share the same Redis instance.11 Django’s Redis cache backend is built on top of `redis-py`, which means Redis connections created by Django are currently indistinguishable from other `redis-py`-based clients in shared Redis deployments. This makes it harder for Redis operators to attribute traffic, diagnose issues, or understand cache usage patterns when multiple applications or frameworks share the same Redis instance. 12 12 13 13 == Proposal == … … 15 15 Django could provide '''additional, non-invasive client identification''' for Redis cache connections to indicate that the connection originates from Django’s cache framework. 16 16 17 ` `redis-py`` exposes a ``driver_info`` API that may be used to attach Django-specific context to the connection, in line with Redis’s client identification recommendations.17 `redis-py` exposes a `driver_info` API that may be used to attach Django-specific context to the connection, in line with Redis’s client identification recommendations. 18 18 19 19 == Goals == … … 27 27 A Redis connection created by Django’s cache backend might expose metadata equivalent to: 28 28 29 * Client library: ` `redis-py``30 * Framework / driver: ``django-cache``29 * Client library: `redis-py` 30 * Framework: `django-cache` 31 31 32 32 == Scope == … … 34 34 * This is a '''feature proposal''', not a patch submission 35 35 * No behavioral changes to caching semantics are proposed 36 * Any implementation would rely solely on ` `redis-py``’s supported APIs36 * Any implementation would rely solely on `redis-py`’s supported APIs