Logging trace events for CLI commands

When someone is using the CLI to make changes to the database, the team operating the cluster may want centralized logging on this. This may be necessary for compliance with security requirements, or it may just be desirable as a check for unauthorized access to the cluster. Can we add some kind of centralized logging for these kind of commands?

Ideally, I think we would want to log the command, the IP it came from, and a summary of the certificate that was used to access the cluster.

The issue names no files, tests, or specific entry points. Start by locating the CLI command handling and existing cluster logging or certificate-authentication paths, then define the audit event contents and centralized logging destination before implementing and testing the feature.

Written by the indexing model from the issue text.