Re: How to Protect Tracing Requests From Client Side

Thanks Guys! This really helps! On Fri, Mar 23, 2018 at 7:10 AM, Mick Semb Wever wrote: > Is there a way to protect C* on the server side from tracing commands that >> are executed from clients? >> > > > If you really needed a way to completely disable all and any

Re: How to Protect Tracing Requests From Client Side

> > Is there a way to protect C* on the server side from tracing commands that > are executed from clients? > If you really needed a way to completely disable all and any possibility of tracing you could start each C* node with tracing switched to a noop implementation. eg, add to the

Re: How to Protect Tracing Requests From Client Side

`nodetool settraceeprobability` controls the *automated* tracing within a single node based on the value set. It may be some or none, but it doesn't effect queries which are explicitly marked for tracing by the driver within your application. You can test this by running CQLSH and enabling TRACING

Re: How to Protect Tracing Requests From Client Side

Thanks a lot Rahul! :-) On Thu, Mar 22, 2018 at 8:03 PM, Rahul Singh wrote: > Execute ‘nodetool settraceprobability 0’ on all nodes. It does zero > percentage of he tracing. > > -- > Rahul Singh > rahul.si...@anant.us > > Anant Corporation > > On Mar 22, 2018,

Re: How to Protect Tracing Requests From Client Side

Execute ‘nodetool settraceprobability 0’ on all nodes. It does zero percentage of he tracing. -- Rahul Singh rahul.si...@anant.us Anant Corporation On Mar 22, 2018, 11:10 AM -0500, shalom sagges , wrote: > Hi All, > > Is there a way to protect C* on the server side from

How to Protect Tracing Requests From Client Side

Hi All, Is there a way to protect C* on the server side from tracing commands that are executed from clients? Thanks!