[
https://issues.apache.org/jira/browse/CASSANDRA-12151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471316#comment-16471316
]
Vinay Chella commented on CASSANDRA-12151:
------------------------------------------
{quote}
Why do you want this to be inconsistent? What is the argument for allowing
this one field, of all the audit log config, to have an additional mechanism
for configuration?
{quote}
Operators set the logging directory different from data directory, consistent
across the nodes and consolidated location for all logs (debug logs, system
logs, gc logs and audit logs), hence followed the same convention that is
followed for configuring other log locations and without extra step to
configure audit log location. However, considering everyone might not follow
the same or operator thinks it is additional/ different mechanism for auditlog,
this location can also be configured using yaml along with other auditlog
configs if they would like to, they don't necessarily need to follow the
convention of setting log location via an environment variable, they can choose
to set it via yaml too. We are consolidating all logs here by managing/
controlling the location via an environment variable, so we end up using the
environment variable. It just avoids yet another location(directory)
configuration to manage. Hopefully, this gives the background.
> 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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
