[jira] [Commented] (CASSANDRA-12151) Audit logging for database activity

["stefan setyadi (JIRA)" <ji...@apache.org>]

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

stefan setyadi commented on CASSANDRA-12151:
--------------------------------------------

Hi this is my first time submitting a patch to jira so tell me if there's anything I can improve on.
I attached a patch for feedback, do tell me if I should change my approach.

to start the logging put {noformat}audit_log: true{noformat} in cassandra.yaml

for now, a summary of what I've done:
* I created keyspace and column families to be initialize at server start.
* Right now it's also logging queries by cassandra itself.
* I didn't put the connections attempt as we can get that information from the clientstate when processing the statement.
* the activity type is just the class name of the statement.
* the column family value when creating keyspace is 'null' as in string value

I haven't tested this on prepared and batch statement.
any feedback is welcome, regards

> Audit logging for database activity
> -----------------------------------
>
>                 Key: CASSANDRA-12151
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12151
>             Project: Cassandra
>          Issue Type: New Feature
>            Reporter: stefan setyadi
>             Fix For: 3.x
>
>         Attachments: 12151.txt
>
>
> we would like a way to enable cassandra to log database activity being done on our server.
> It should show username, remote address, timestamp, action type, keyspace, column family, and the query statement.
> it should also be able to log connection attempt and changes to the user/roles.
> I was thinking of making a new keyspace and insert an entry for every activity that occurs.
> Then It would be possible to query for specific activity or a query targeting a specific keyspace and column family.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)