[
https://issues.apache.org/jira/browse/CASSANDRA-12151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16383606#comment-16383606
]
Jason Brown commented on CASSANDRA-12151:
-----------------------------------------
I agree with [~djoshi3] and [~jjordan]: this functionality should really
leverage the existing behavior of FQL (CASSANDRA-13893). There is no need to
create a parallel or duplicate set of behaviors, unless it's completely
warranted - and I have heard no arguments here that it is.
Further, I like [~djoshi3]'s idea about adding a pluggable component that we
can fit into the client-facing netty pipeline. It allows somebody to go bananas
adding audit checks/details, and yet leaves untouched the standard behavior
that 99.9% of users expect.
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
