[ 
https://issues.apache.org/jira/browse/CASSANDRA-16682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17349420#comment-17349420
 ] 

Sarma Pydipally edited comment on CASSANDRA-16682 at 5/21/21, 6:03 PM:
-----------------------------------------------------------------------

got it ... i was not aware of the original design and decisions.

we should not introduce new flow before the major release.

please leave the new entries in logback.xml in COMMENTED OUT section.


was (Author: oramad):
got it ... i was not aware of the original design and decisions.

we should not introduce new flow before the major release.

please leave the new entries in logback.xml in COMMENTED OUT setion.

> Cassandra 4.0 RC1 ... Audit Logs going to wrong location
> --------------------------------------------------------
>
>                 Key: CASSANDRA-16682
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-16682
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Tool/auditlogging
>            Reporter: Sarma Pydipally
>            Assignee: Ekaterina Dimitrova
>            Priority: Normal
>             Fix For: 4.0-rc
>
>
> Version : Cassandra 4.0 RC1
> Settings in my : <CASSANDRA_HOME>/conf/cassandra.yaml 
> {code:yaml}
> audit_logging_options: 
>     enabled: true
>      logger: 
>       - class_name: FileAuditLogger
>      excluded_categories: QUERY, DML
>      audit_logs_dir: "/apps/opt/cassandra/logs/audit"
>      roll_cycle: DAILY
>      block: false
> {code}
>  After restart of Cassandra ... I can see the Audit Logs. But they are going 
> into system.log and debug.log. They are NOT going into 
> {noformat}
> "/apps/opt/cassandra/logs/audit/audit.log"{noformat}
>  
> Also noticed that : it does not ignore the "excluded_categories" and logs 
> everything ...



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to