Upstash Documentation

ACL LOG

Show the ACL log entries.
2 min read

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#

ArgumentRequiredRepeatableDescription
countNoNoMaximum number of log entries to return.
RESETNoNoClear the log instead of reading it.

Important points#

  • ACL LOG currently always returns an empty array; this deployment does not yet track authentication or permission failures.
  • ACL LOG RESET still returns OK.

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.

ProtocolReply
RESP2Array (currently always empty); or Simple string OK for RESET
RESP3Array (currently always empty); or Simple string OK for RESET
Note

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
Note

This command is not supported yet in @upstash/redis.

upstash_redis
Note

This command is not supported yet in upstash_redis.

ioredis
node-redis
redis-py
go-redis
jedis
redis-rs