[
https://issues.apache.org/jira/browse/CASSANDRA-12151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16322253#comment-16322253
]
Stefan Podkowinski commented on CASSANDRA-12151:
------------------------------------------------
I took a different approach with CASSANDRA-13668 by proposing to send auditing
events to external subscribers that would be able to store or analyze them
further. It's a different approach from storing auditing events in a local or
distributed keyspace, as implemented in this ticket. My assumption was
basically that raising alerts on certain events would be easier and more
efficient to implement, if consumed by an external client, compared to polling
a table. But I'm curious how any discussion as part of this ticket will turn
out and what the different requirements are.
> 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: 4.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.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
