[
https://issues.apache.org/jira/browse/CASSANDRA-12151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16386288#comment-16386288
]
Ariel Weisberg commented on CASSANDRA-12151:
--------------------------------------------
I think logging more things to more formats, and making what is logged more
configurable are great additions. I'm -1 on having two approaches to logging
database access to a file that are redundant.
I don't really care what implementation we go with just that there aren't two.
You could completely remove the existing FQL since we haven't shipped it and
replace it with something with a similar high performance asynchronous binary
logging option as well as the text based one you think is best for audit logs.
Or you can iterate on the existing FQL functionality to get what you want from
it.
Chronicle has a human and machine readable text format. Switching between the
two is a flag. You could use the existing full query log plumbing to write one
of those if you wanted. You can also convert binary logs to human readable logs
using fqltool. You can also tail the full query log in human readable format
using fqltool. I think binary vs text is a bit of a red herring.
Some things a new implementation needs to preserve is support for asynchronous
logging, bounded memory utilization for queueing, and a reasonably efficient
approach to appending to a file from multiple threads. It should be possible
for a beefy node to log all the operations a node is executing and process them
using a single core if configured to use binary format.
> 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: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
