cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stefan setyadi (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-12151) Audit logging for database activity
Date Fri, 29 Jul 2016 04:34:20 GMT


stefan setyadi commented on CASSANDRA-12151:

yeah sure, sorry for going ahead and doing my own thing.

# I was thinking of global one as it would be easier to be queried. it would also help in
case any of the server fails as we probably don't want to lose the logs.
# can I ask for clarification on what you meant by every query? at the very least we want
to know the usual "who did what and when". Maybe have different levels/choice for which query
are logged? In the end the trade off between performance and log is something which I'd rather
leave on the hands of the company using it.

> 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