cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tyler Hobbs <ty...@datastax.com>
Subject Re: User audit in Cassandra
Date Sat, 10 Jan 2015 00:37:07 GMT
system_traces is for query tracing, which is for diagnosing performance
problems, not logging activity.

Cassandra is designed to allow you to write your own Authenticator pretty
easily.  You can just subclass PasswordAuthenticator and add logging where
desired.  Compile that into a jar, put it in the lib/ directory for
Cassandra, and change cassandra.yaml to use that class.

On Thu, Jan 8, 2015 at 6:34 AM, Ajay <ajay.garga@gmail.com> wrote:

> Hi,
>
> Is there a way to enable user audit or trace if we have enabled
> PasswordAuthenticator in cassandra.yaml and set up the users as well. I
> noticed there are keyspaces system_auth and system_trace. But there is no
> way to find out which user initiated which session. Is there anyway to find
> out?. Also is it recommended to enable system_trace in production or to
> know how many sessions started by a user?
>
> Thanks
> Ajay
>



-- 
Tyler Hobbs
DataStax <http://datastax.com/>

Mime
View raw message