cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From anuja jain <anujaja...@gmail.com>
Subject Re: Can we get username and timestamp in cqlsh_history?
Date Wed, 12 Apr 2017 11:50:11 GMT
Thanks Nicolas. That is exactly what I was looking for.

On Tue, Apr 4, 2017 at 12:08 AM, Durity, Sean R <SEAN_R_DURITY@homedepot.com
> wrote:

> Sounds like you want full auditing of CQL in the cluster. I have not seen
> anything built into the open source version for that (but I could be
> missing something). DataStax Enterprise does have an auditing feature.
>
>
>
>
>
> Sean Durity
>
>
>
> *From:* anuja jain [mailto:anujajain4@gmail.com]
> *Sent:* Wednesday, March 29, 2017 7:37 AM
> *To:* user@cassandra.apache.org
> *Subject:* Can we get username and timestamp in cqlsh_history?
>
>
>
> Hi,
>
> I have a cassandra cluster having a lot of keyspaces and users. I want to
> get the history of cql commands along with the username and the time at
> which the command is run.
>
> Also if we are running some commands from GUI tools like
> Devcenter,dbeaver, can we log those commands too? If yes, how?
>
>
>
> Thanks,
>
> Anuja
>
> ------------------------------
>
> The information in this Internet Email is confidential and may be legally
> privileged. It is intended solely for the addressee. Access to this Email
> by anyone else is unauthorized. If you are not the intended recipient, any
> disclosure, copying, distribution or any action taken or omitted to be
> taken in reliance on it, is prohibited and may be unlawful. When addressed
> to our clients any opinions or advice contained in this Email are subject
> to the terms and conditions expressed in any applicable governing The Home
> Depot terms of business or client engagement letter. The Home Depot
> disclaims all responsibility and liability for the accuracy and content of
> this attachment and for any damages or losses arising from any
> inaccuracies, errors, viruses, e.g., worms, trojan horses, etc., or other
> items of a destructive nature, which may be contained in this attachment
> and shall not be liable for direct, indirect, consequential or special
> damages in connection with this e-mail message or its attachment.
>

Mime
View raw message