ACL LOG
Syntax
ACL LOG [count | RESET]
- Available since:
- 6.0.0
- Time complexity:
- O(N) with N being the number of entries shown.
- ACL categories:
-
@admin
,@slow
,@dangerous
,
The command shows a list of recent ACL security events:
- Failures to authenticate their connections with
AUTH
orHELLO
. - Commands denied because against the current ACL rules.
- Commands denied because accessing keys not allowed in the current ACL rules.
The optional argument specifies how many entries to show. By default
up to ten failures are returned. The special RESET
argument clears the log.
Entries are displayed starting from the most recent.
Examples
> AUTH someuser wrongpassword
(error) WRONGPASS invalid username-password pair
> ACL LOG 1
1) 1) "count"
2) (integer) 1
3) "reason"
4) "auth"
5) "context"
6) "toplevel"
7) "object"
8) "AUTH"
9) "username"
10) "someuser"
11) "age-seconds"
12) "8.038"
13) "client-info"
14) "id=3 addr=127.0.0.1:57275 laddr=127.0.0.1:6379 fd=8 name= age=16 idle=0 flags=N db=0 sub=0 psub=0 ssub=0 multi=-1 qbuf=48 qbuf-free=16842 argv-mem=25 multi-mem=0 rbs=1024 rbp=0 obl=0 oll=0 omem=0 tot-mem=18737 events=r cmd=auth user=default redir=-1 resp=2"
15) "entry-id"
16) (integer) 0
17) "timestamp-created"
18) (integer) 1675361492408
19) "timestamp-last-updated"
20) (integer) 1675361492408
Each log entry is composed of the following fields:
count
: The number of security events detected within a 60 second period that are represented by this entry.reason
: The reason that the security events were logged. Eithercommand
,key
,channel
, orauth
.context
: The context that the security events were detected in. Eithertoplevel
,multi
,lua
, ormodule
.object
: The resource that the user had insufficient permissions to access.auth
when the reason isauth
.username
: The username that executed the command that caused the security events or the username that had a failed authentication attempt.age-seconds
: Age of the log entry in seconds.client-info
: Displays the client info of a client which caused one of the security events.entry-id
: The sequence number of the entry (starting at 0) since the server process started. Can also be used to check if items were “lost”, if they fell between periods.timestamp-created
: A UNIX timestamp inmilliseconds
at the time the entry was first created.timestamp-last-updated
: A UNIX timestamp inmilliseconds
at the time the entry was last updated.
RESP2/RESP3 Reply
When called to show security events:
- Array reply: an array of Bulk string reply elements representing ACL security events.
When called with
RESET
: - Simple string reply:
OK
if the security log was cleared.
History
- Starting with Redis version 7.2.0: Added entry ID, timestamp created, and timestamp last updated.