cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-12151) Audit logging for database activity
Date Thu, 28 Jul 2016 13:40:20 GMT


Jonathan Ellis commented on CASSANDRA-12151:

Can we back up a little and talk about design?

Some questions in my mind:

# Do we want a global audit log, or server-local?  If the former (easier for users to query),
it should go in system_distributed keyspace; otherwise just in system (higher performance).
# Is there a use case where you'd want to log every query?  That seems like it would entail
a prohibitive performance penalty.  I would think most users would be better served by logging
meta-changes (adding roles, altering tables, etc)

> Audit logging for database activity
> -----------------------------------
>                 Key: CASSANDRA-12151
>                 URL:
>             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

View raw message