Use ACL LOG to inspect recent authentication and permission failures, and ACL LOG RESET to clear it.
On standard Redis this is where to look when a client is unexpectedly denied: each entry records the reason, the username, and the command or key involved. This deployment does not yet record ACL failures, so ACL LOG currently always returns an empty array regardless of the optional count, while ACL LOG RESET still succeeds.
Syntax#
Arguments#
| Argument | Required | Repeatable | Description |
|---|---|---|---|
count | No | No | Maximum number of log entries to return. |
RESET | No | No | Clear the log instead of reading it. |
Important points#
ACL LOGcurrently always returns an empty array; this deployment does not yet track authentication or permission failures.ACL LOG RESETstill returnsOK.
Response#
The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
| Protocol | Reply |
|---|---|
| RESP2 | Array (currently always empty); or Simple string OK for RESET |
| RESP3 | Array (currently always empty); or Simple string OK for RESET |
Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
Examples#
TCP examples use the TLS REDIS_URL from the Upstash console. REST examples use UPSTASH_REDIS_REST_URL and UPSTASH_REDIS_REST_TOKEN.
Redis CLI
@upstash/redis
This command is not supported yet in @upstash/redis.
upstash_redis
This command is not supported yet in upstash_redis.