cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stefan setyadi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-12151) Audit logging for database activity
Date Mon, 01 Aug 2016 12:15:20 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-12151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15401929#comment-15401929
] 

stefan setyadi commented on CASSANDRA-12151:
--------------------------------------------

After some discussion with my team, we were thinking of the idea of being able to configure
the log to each keyspace or table.
And so I propose:
# Cassandra will still log meta-changes of the server
# We can configure it to log every query (update/read) which targets a specific keyspace or
table. For our use case, we need to log it even knowing that there will be some performance
penalty.

all in all, the ability to configure which query will be logged will be helpful in cases where
* the table is important, such as employee data, financial information, etc
* or where we know the table won't be accessed as much

> 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: 3.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.3.4#6332)

Mime
View raw message