cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinay Chella (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CASSANDRA-12151) Audit logging for database activity
Date Wed, 09 May 2018 08:04:00 GMT

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

Vinay Chella edited comment on CASSANDRA-12151 at 5/9/18 8:03 AM:
------------------------------------------------------------------

Hi [~jasobrown] ,

Yes, we can set audit_logs_dir either from -D jvm arg or from {{cassandra.yaml}} - {{audit_logging_options::audit_logs_dir}}.
Idea is to be inconsistent with rest of the project's log configuration process by setting
them via {{-D jvm arg}}, hence naming is kept inconsistent with logs - {{cassandra.logdir.audit}}.
I have also updated the documentation for the same.
{quote}Operators cannot, in an obvious manner, adjust the following AuditLogOptions options:
audit_logs_dir/block/max_queue_weight/max_log_size/roll_cycle. They are basically hidden yaml
options: you can set them, but you have to know they exist. I understand these are more advanced
options, but we should document them either in the yaml or the doc page.
{quote}
Yes, they intentionally kept there for advanced configurations. Agree with you on documenting
them. Updated the documentation for this.

 
||*Branch*||*PR*||*uTest*||
|[trunk_CASSANDRA-12151|https://github.com/vinaykumarchella/cassandra/tree/trunk_CASSANDRA-12151]|[PR
for trunk|https://github.com/vinaykumarchella/cassandra/pull/2/commits]|[!https://circleci.com/gh/vinaykumarchella/cassandra/tree/trunk_CASSANDRA-12151.svg?style=svg!|https://circleci.com/gh/vinaykumarchella/cassandra/tree/trunk_CASSANDRA-12151]|


was (Author: vinaykumarcse):
Hi Jason,

Yes, we can set audit_logs_dir either from -D jvm arg or from {{cassandra.yaml}} - {{audit_logging_options::audit_logs_dir}}.
Idea is to be inconsistent with rest of the project's log configuration process by setting
them via   {{-D jvm arg}}, hence naming is kept inconsistent with logs - {{cassandra.logdir.audit}}.
I have also updated the documentation for the same.

{quote}Operators cannot, in an obvious manner, adjust the following AuditLogOptions options:
audit_logs_dir/block/max_queue_weight/max_log_size/roll_cycle. They are basically hidden yaml
options: you can set them, but you have to know they exist. I understand these are more advanced
options, but we should document them either in the yaml or the doc page.
{quote}
Yes, they intentionally kept there for advanced configurations. Agree with you on documenting
them. Updated the documentation for this.

 
||*Branch*||*PR*||*uTest*||
|[trunk_CASSANDRA-12151|https://github.com/vinaykumarchella/cassandra/tree/trunk_CASSANDRA-12151]|[PR
for trunk|https://github.com/vinaykumarchella/cassandra/pull/2/commits]|[!https://circleci.com/gh/vinaykumarchella/cassandra/tree/trunk_CASSANDRA-12151.svg?style=svg!|https://circleci.com/gh/vinaykumarchella/cassandra/tree/trunk_CASSANDRA-12151]|

> 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


Mime
View raw message