Surprising. Feels like something that should change. If it’s enabled in yaml, why WOULDNT we want it started on start?
> On Jan 14, 2025, at 7:40 AM, Štefan Miklošovič <smikloso...@apache.org> wrote: > > Hi Sebastian, > > the behaviour you see seems to be a conscious decision: > > https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/audit/AuditLogManager.java#L204 > > On Tue, Jan 14, 2025 at 4:21 PM Sebastian Albrecht > <sebastian.albre...@agido.com <mailto:sebastian.albre...@agido.com>> wrote: >> Hi, >> i am using cassandra 4.1 and i want activate audit logging. I set the >> following values in cassandra.yml and expect that logging starts after the >> next cassandra start: >> audit_logging_options: >> enabled: true >> logger: >> - class_name: FileAuditLogger >> included_categories: DCL, ERROR, AUTH >> >> After startup it is also logging: AuditLogManager.java:77 - Audit logging is >> enabled. >> But when i emit an event that should appear in the audit log (i.e. try login >> with wrong password), i do not see it. I have to explicitly enable it via >> nodetool for the audit logs to be seen. After cassandra restart it seems to >> be disabled again. >> Anyone also came across that? >> >> Thx, >> Sebastian.
