You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Stefan Podkowinski (JIRA)" <ji...@apache.org> on 2018/04/05 13:26:00 UTC
[jira] [Comment Edited] (CASSANDRA-12151) Audit logging for
database activity
[ https://issues.apache.org/jira/browse/CASSANDRA-12151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16426915#comment-16426915 ]
Stefan Podkowinski edited comment on CASSANDRA-12151 at 4/5/18 1:25 PM:
------------------------------------------------------------------------
I was just giving the BinLogger a try and it looks like the way the bin log files are created, should make it possible to archive them before they get deleted. The most simple way would probably to run a rsync job for pulling the latest chronicle bin logs from the nodes. The timestamp based naming of the files should make this trivial.
Another option would be to allow the user to configure an archival script that will be executed in {{BinLog.onReleased(cycle, file)}} for every deleted bin log, just as we do in {{CommitLogArchiver}}. WDYT [~aweisberg]?
I'm going to write a custom {{IAuditLogger}} implementation tomorrow and will get back with some more feedback.
was (Author: spodxx@gmail.com):
I was just giving the BinLogger a try and it looks like the way the bin log files are created, should make it possible to archive them before they get deleted. The most simple way would probably to run a rsync job for pulling the latest chronicle bin logs from the nodes. The timestamp based naming of the files should make this trivial.
Another option would be to allow the user to configure an archival script that will be executed in {{BinLog.onReleased(cycle, file)}} for every deleted bin log, just as we do in {{CommitLogArchiver}}. WDYT [~aweisberg]?
I'm going to write a custom implementation tomorrow and will get back with some more feedback.
> 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, CASSANDRA_12151-benchmark.html, 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-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org