Time to Complete
Audit logging records information about changes made to a database. Enterprises use audit logs to track who made changes, what data changed and when changes were made. This data is crucial for:
Audit logging has access to the information shown here. The default behavior is to write all of the fields to the log.
Audit logging is disabled by default in Cassandra. There are two ways to configure audit logging: dynamically using nodetool or statically using cassandra.yaml. A configuration using nodetool overrides a configuration defined in cassandra.yaml and does not persist across server restarts.Next: Configurable Properties
Use excludes to limit logs to the information actually required.
Use the operating system to control access to log files containing sensitive data.
Manually redact sensitive data before sharing log files.Next: Skill Building
Are you ready to try it out?
Cassandra 4.x audit logging enables enterprises to track activity in their database.