Re: Client ID logging

[Andy Tolbert]

CASSANDRA-13665 
adds a 'nodetool clientlist' command which I think would be helpful in this
circumstance.  That feature is targeted for C* 4.0 however.

You could use something like lsof  to
see what active TCP connections there are to the host servers running your
C* cluster to capture the IP addresses of the clients connected to your
cluster.

Thanks,
Andy

On Mon, May 21, 2018 at 1:42 PM, Hannu Kröger  wrote:

> Hmm, I think that by default not but you can create a hook to log that.
> Create a wrapper for PasswordAuthenticator class for example and use that.
> Or if you don’t use authentication you can create your own query handler.
>
> Hannu
>
> James Lovato  kirjoitti 21.5.2018 kello 21.37:
>
> Hi guys,
>
>
>
> Can standard OSS Cassandra 3 do logging of who connects to it?  We have a
> cluster in 3 DCs and our devs want to see if the client is crossing across
> DC (even though they have DCLOCAL set from their DS driver).
>
>
>
> Thanks,
> James
>
>

Re: Client ID logging

[Hannu Kröger]

Hmm, I think that by default not but you can create a hook to log that. Create 
a wrapper for PasswordAuthenticator class for example and use that. Or if you 
don’t use authentication you can create your own query handler.

Hannu

> James Lovato  kirjoitti 21.5.2018 kello 21.37:
> 
> Hi guys,
>  
> Can standard OSS Cassandra 3 do logging of who connects to it?  We have a 
> cluster in 3 DCs and our devs want to see if the client is crossing across DC 
> (even though they have DCLOCAL set from their DS driver).
>  
> Thanks,
> James

Client ID logging

[James Lovato]

Hi guys,

Can standard OSS Cassandra 3 do logging of who connects to it?  We have a 
cluster in 3 DCs and our devs want to see if the client is crossing across DC 
(even though they have DCLOCAL set from their DS driver).

Thanks,
James