Dinesh Joshi commented on CASSANDRA-12151:

Hi [~eanujwa] - I did review the design. As you can see there are different 
perspectives on the Audit functionality - granularity, type etc. Personally, 
defining an interface for Auditing would help keep things generic. For example, 
based on your needs you could, in theory, have an Audit logger implementation 
that logs at the keyspace or table level or even make more sophisticated 
decisions. It frees up everyone to define the Audit implementation to their 
specific needs. Bear in mind that you do not want to degrade performance for 
users that do not use Auditing capabilities.

> 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
>            Assignee: Vinay Chella
>            Priority: Major
>             Fix For: 4.x
>         Attachments: 12151.txt, 
> DesignProposal_AuditingFeature_ApacheCassandra_v1.docx
> 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

To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to