You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What are your thoughts about adding the ACL user to monitor @antirez
I think this information may be useful for those debugging that are leveraging some of the complexity of ACLs. For example, when debugging commands it would be helpful to see the user to help determine if an ACLs command or keyspace restrictions is the culprit. While the error message for acls are very clear, if you are debugging from an application perspective it may be helpful to understand the commands issued & by what user to help with the complexity of access controls.
Thoughts?
The text was updated successfully, but these errors were encountered:
Error-generating commands (including NOPERM) are not shown in MONITORs output, so I can't see how it will help in debugging as you've suggested. That said, I think that adding the ACL user to MONITOR is a good idea - we already show the connection details.
Note that this modification will break backward compatibility, so some care is needed to think if/how to resolve this.
What are your thoughts about adding the ACL user to monitor @antirez
I think this information may be useful for those debugging that are leveraging some of the complexity of ACLs. For example, when debugging commands it would be helpful to see the user to help determine if an ACLs command or keyspace restrictions is the culprit. While the error message for acls are very clear, if you are debugging from an application perspective it may be helpful to understand the commands issued & by what user to help with the complexity of access controls.
Thoughts?
The text was updated successfully, but these errors were encountered: