Re: Logging queries

Thanks Bhuvan! Matija, I'm looking forward to this new release. Cassandra-diagnostics is just great and this feature will make it awesome. Hope to hear from you soon. 2017-02-18 17:20 GMT-03:00 Bhuvan Rawal : > Im not sure if you can create an index on system_traces keyspace for this > use case.

Re: Logging queries

Im not sure if you can create an index on system_traces keyspace for this use case. If the performance issue that you are trying to troubleshoot is consistent than you can switch on tracing for a while and do dump of system_traces.events table say using COPY into csv. You can do analysis on that f

Re: Logging queries

Hi Igor, Your best bet is to wait for our next release of diagnostics for 2.x branch. We are planning it for next week. Best, Matija On Sat, Feb 18, 2017 at 8:58 PM, Igor Leão wrote: > Hi Bhuvan, > Thanks a lot! > > Any idea if something

Re: Logging queries

Hi Bhuvan, Thanks a lot! Any idea if something can be done for C* 2.X? Best, Igor 2017-02-18 16:41 GMT-03:00 Bhuvan Rawal : > Hi Igor, > > If you are using java driver, you can log slow queries on client side > using QueryLogger. > https://docs.datastax.com/en/developer/java-driver/2.1/manual/l

Re: Logging queries

Hi Igor, If you are using java driver, you can log slow queries on client side using QueryLogger. https://docs.datastax.com/en/developer/java-driver/2.1/manual/logging/ Slow Query logger for server was introduced in C* 3.10 version. Details: https://issues.apache.org/jira/browse/CASSANDRA-12403

Re: Logging

Sam, Paulo, One more question on logging. Can I add IP and hostname to the log message? If it is possible, can you give me example of how I would need to change %-5level %date{HH:mm:ss,SSS} %msg%n to add this information? Thanks, Oleg On Tue, Jan 26, 2016 at 4:42 PM, oleg yusim wrote: > Sam

Re: Logging

Sam, Paulo, Thank you very much for explanations and references. Oleg On Mon, Jan 25, 2016 at 10:08 AM, Sam Tunnicliffe wrote: > Paulo is correct in saying that C* doesn't have a direct equivalent of > SecurityContextHolder. Authenticated principal info is retrievable from the > QueryState dur

Re: Logging

Paulo is correct in saying that C* doesn't have a direct equivalent of SecurityContextHolder. Authenticated principal info is retrievable from the QueryState during query execution but a) this isn't available to every method in the call chain and b) its scope is limited to the coordinator for the r

Re: Logging

That would work, but afaik Cassandra doesn't have an equivalent of RequestContextHolder/SecurityContextHolder that is able to retrieve the user/session of a given thread/request (maybe I'm wrong as I'm no auth expert), so if these don't exist we'd need to add equivalent to those or do it via MDC (s

Re: Logging

Paulo, Ideally - all the actions (security purposes, preserving completness of the audit trail). How about this approach: http://www.codelord.net/2010/08/27/logging-with-a-context-users-in-logback-and-spring-security/ ? Would that work? Or you would rather suggest to go MDC way? Thanks, Oleg On

Re: Logging

What kind of actions? nodetool/system actions or cql statements? You could probably achieve identity-based logging with logback Mapped Diagnostic Context (MDC - logback.qos.ch/manual/mdc.html), but you'd need to patch your own Cassandra jars in many locations to provide that information to the log

Re: Logging

I want to try to re-phrase my question here... what I'm trying to achieve is identity-based logging. I.e. every log message in file should start with username of the user, who initiated this action. Would that be possible to achieve? If so, can you give me a brief example? Thanks, Oleg On Thu, J

Re: Logging

Joel, Thanks for reference. What I'm trying to achieve, is to add the name of the user, who initiated logged action. I tried c{5}, but what I see is that; TRACE [GossipTasks:1] c{5} 2016-01-21 20:51:17,619 Gossiper.java:700 - Performing status check ... I think, I'm missing something here. Any s

Re: Logging

Cassandra uses logback as its backend for logging. You can find information about configuring logging in Cassandra by searching for "Configuring logging" on docs.datastax.com and selecting the documentation for your version. The documentation for PatternLayouts (the pattern string about which you

Re: Logging client ID for YCSB workloads on Cassandra?

Sure. I updated the YCSB code to pass a client ID as input parameter and then stored the clientID in the properties and used it in the DBWrapper class for logging per operation *YCSB/core/src/main/java/com/yahoo/ycsb/DBWrapper.java* Please let me know if you need more information and I can share m

Re: Logging client ID for YCSB workloads on Cassandra?

HI Jatin;  besides enabling Tracing,   is there any other way to get the task done  ?  (to log the client ID for every operation)Please share with the community the solution, so that we could collectively learn from your experience.  cheersJan/ On Friday, February 20, 2015 12:48 PM, Jatin

Re: Logging client ID for YCSB workloads on Cassandra?

Never mind, got it working. Thanks :) — Jatin Ganhotra Graduate Student, Computer Science University of Illinois at Urbana Champaign http://jatinganhotra.com http://linkedin.com/in/jatinganhotra On Wed, Feb 18, 2015 at 7:09 PM, Jatin Ganhotra wrote: > Hi, > > I'd like to log the client ID for

Re: logging over multi-datacenter

ok thank you. 2014-11-20 16:02 GMT+01:00 Mark Reddy : > Hi Adil, > > When using the default superuser ('cassandra') a consistency level of > QUORUM is used. When using other users ONE is used. > > You are not supposed to use 'cassandra' user directly, except to create > another superuser and use

Re: logging over multi-datacenter

Hi Adil, When using the default superuser ('cassandra') a consistency level of QUORUM is used. When using other users ONE is used. You are not supposed to use 'cassandra' user directly, except to create another superuser and use that one from that point on. Mark On 20 November 2014 14:40, Adil

Re: logging over multi-datacenter

cassandra version 2.1.2 with the default user we create another user and with this one we could login even if only one node is up 2014-11-20 15:16 GMT+01:00 Mark Reddy : > Hi Adil, > > What Cassandra version are you using? Are you using the default user or a > non-default user? > > > Mark > > On

Re: logging over multi-datacenter

Hi Adil, What Cassandra version are you using? Are you using the default user or a non-default user? Mark On 20 November 2014 08:20, Adil wrote: > Hi, > We have two data-center, we configured PasswordAuthenticator on each node, > we increment the RF of system_auth to the number of nodes (each

Re: Logging of triggers

I found now that i logged with a too low log level set so it was filtered from the system log. Logging with a more critical log level made the log messages appear in the system log. /Joel 2014-06-03 16:30 GMT+02:00 Joel Samuelsson : > I'm testing triggers as part of a project and would like to

Re: Logging Cassandra Reads/Writes

Aaron, Thanks for the references! I'll try the things you mentioned and see how it goes! Best, Mohammad On Wed, Jul 10, 2013 at 8:07 PM, aaron morton [via cassandra-u...@incubator.apache.org] < ml-node+s3065146n7588930...@n2.nabble.com> wrote: > Some info on request tracing > http://www.datast

Re: Logging Cassandra Reads/Writes

Some info on request tracing http://www.datastax.com/dev/blog/tracing-in-cassandra-1-2 > 1) Is it possible to log which node provides the real data in a read > operation? It's available at the DEBUG level of logging. You probably just want to enable it on the org.apache.cassandra.db.StorageProx

Re: Logging Cassandra Reads/Writes

There is a new tracing feature in Cassandra 1.2 that might help you with this. On Tue, Jul 9, 2013 at 1:31 PM, Blair Zajac wrote: > No idea on the logging, I'm pretty new to Cassandra. > > Regards, > Blair > > On Jul 9, 2013, at 12:50 PM, hajjat wrote: > > > Blair, thanks for the clarification!

Re: Logging Cassandra Reads/Writes

No idea on the logging, I'm pretty new to Cassandra. Regards, Blair On Jul 9, 2013, at 12:50 PM, hajjat wrote: > Blair, thanks for the clarification! My friend actually just told me the > same.. > > Any idea on how to do logging?? > > Thanks! > > > > -- > View this message in context: > h

Re: Logging Cassandra Reads/Writes

Blair, thanks for the clarification! My friend actually just told me the same.. Any idea on how to do logging?? Thanks! -- View this message in context: http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Logging-Cassandra-Reads-Writes-tp7588893p7588896.html Sent from the cassand

Re: Logging Cassandra Reads/Writes

On 07/09/2013 12:25 PM, hajjat wrote: Hi, In a quorum read, my understanding is that Cassandra gets a digest of the object to be read from all nodes, and then chooses the fastest node for retrieving the data (if the quorum is met). According to this talk at Cassandra summit, that's incorrect.

Re: Logging Cassandra queries

> (but still the list of classes would be helpful :) ) The source code is the most up to date list of the classes. This is a talk I did on Cassandra Internals at Apache Con in Feb 2013, unfortunately it looks like the videos will never be released owing to technical snafu's http://www.slideshar

Re: Logging Cassandra queries

sure, i think it'd be a useful feature On Sat, May 18, 2013 at 4:13 PM, Tomàs Núnez wrote: > If you're looking for logging like "get keyX with CL quorum and slice Y >> took n millis" > > > That would be even better! Maybe should I file a ticket in Cassandra Jira > for this feature? Do you think

Re: Logging Cassandra queries

> > If you're looking for logging like "get keyX with CL quorum and slice Y > took n millis" That would be even better! Maybe should I file a ticket in Cassandra Jira for this feature? Do you think it would be helpful? BTW, just "get keyX" or "set keyX" would work for me. I'll check org.apache.c

Re: Logging Cassandra queries

If you're looking for logging like "get keyX with CL quorum and slice Y took n millis" there's nothing like that from what I could find. We had to modify c* source (CassandraServer.java) to add this query logging to the thrift codepath. On May 18, 2013 3:20 PM, "Tomàs Núnez" wrote: > Yes, I read

Re: Logging Cassandra queries

Yes, I read how to do that here, as well: http://www.datastax.com/docs/1.1/configuration/logging_options But I didn't know what classes to enable logging for the queries... Is there any document with the list of classes with a bit explanation for each of them? I can't find any, and I don't underst

Re: Logging Cassandra queries

> And... could I be more precise when enabling logging? Because right now, with > log4j.rootLogger=DEBUG,stdout,R I'm getting a lot of information I won't use > ever, and I'd like to enable just what I need to see gets and seds…. see the example at the bottom of this file about setting the log l

Re: logging servers? any interesting in one for cassandra?

Thanks Dean. We'll definitely take a look. (probably in January) -brian --- Brian O'Neill Lead Architect, Software Development Health Market Science The Science of Better Results 2700 Horizon Drive • King of Prussia, PA • 19406 M: 215.588.6024 • @boneill42 •

Re: logging servers? any interesting in one for cassandra?

Sure, in our playing around, we have an awesome log back configuration for development time only that shows warning, severe in red in eclipse and let's you click on every single log taking you right to the code that logged it…(thought you might enjoy it)... https://github.com/deanhiller/playorm/bl

Re: logging servers? any interesting in one for cassandra?

Nice DeanŠ I'm not so sure we would run the server, but we'd definitely be interested in the logback adaptor. (We would then just access the data via Virgil (over REST), with a thin javascript UI) Let me/us know if you end up putting it out there. We intend centralize logging sometime over the n

Re: Logging 'write' operations

In theory you could grab the commit log, you would then have to work with internal cassandra structures to understand what is in there. Otherwise do it at the app level or design it into your data model. Cheers - Aaron Morton Freelance Developer @aaronmorton http://www.thelas