Apache Cassandra Monitoring FastPack
Fastpack Download contains:
The Cassandra Load Dashboard gives an Overview of Client and Server Side performance and Load.
The Fastpack contains a Dashboard and a Template System Profile. In addition it contains a Metric Group for Cassandra JMX Measures, some of which are already subscribed in the system profile. dynaTrace can monitor any JMX attribute available withing Cassandra in addition to those supplied in this fastpack. The System Profile already contains an Agent Group for Cassandra, just add the dynaTrace agent to your JVM_OPTS when starting Cassandra (use name=Cassandra). This agent group contains some minor modifications to allow optimal monitoring of Cassandra. The System profile also contains all necessary Sensors to monitor both Server and client side. Add the Cassandra Common Sensor group in your own agent groups.
Just download and import the FastPack on your Dynatrace Server (see Plugin Management)
If you start with a fresh system simply copy the provided System profile (to give it an application specific name) and add agent groups for your own application. If you want to use Cassandra in an existing System profile please copy the following items to your system profile.
Feel free to contribute any changes on Github
I can't have this FastPack working with .NET client. Does this plugin only works with Java Clients ?
The FastPack works for Java-based Cassandra Client Libraries. Not for .NET in the moment. For .NET you will however see dynatrace automatically pick up the calls in the Cassandra API in case these calls have a performance impact. If you always want to see the calls to the Cassandra API you can define your own custom sensors so that dynatrace always picks them up. Also allows you to capture method arguments of these calls to get more context such as the data you want to query
are you working on a custom sensor for .net? We are looking to see if we can build one, but this will be our first one. Is there some information about how we can build this?
we also would like to do the same for not only Cassandra, but for Mongo as well.
Hi. Currently there are no active plans of building such a Sensor Pack that I am aware of.
If you go ahead and come up with Sensors that work for you feel free to Export that System Profile that contains your Sensor Rules. We can then help you upload this to this page as a FastPack so that others can leverage that is well. If you have any other things you are working on also let us know. Simply send us an email to firstname.lastname@example.org
I have an application that uses Cassandra. A web application is connect to Cassandra DB. I first instrumented the web application and able to see the CQL being sent to Cassandra.
I, then, instrumented the Cassandra server side. After that I downloaded the fast pack and copied the sensor pack, and business transaction over to the existing system profile. The agent is connected fine. I am able to see the host process (CPU, memory, JVM, etc) from monitoring dashboard.
However, when I try to see the pure path from Cassandra sever, I cannot see any. The Cassandra dashboard also show no chart after I changed the source and system profile.
Did I do anything wrong? Please advise. My apology in advance if this is not the place to ask for such advise.
Hi Ron. Could you do me the favor and post this question to http://answers.dynatrace.com?
We sucessfully set up this Cassandra fastpack and every measure appears in the "Cassandra - load" dashboard except for the "Active and Pending Tasks" dashlet.
The following measure do not exist:
Is it a known issue ?
Thanks for your help.
With the Cassandra sensor that's delivered OOTB in the product, is there any value to this Fastpack any longer?
Hi Joe. I just checked with the engineering team. They think that this FastPack is still relevant as the dashboard with these metrics is not yet part of the OOTB Support. Question is whether we should move some of this to the OOTB Product Delivery. For now the FastPack is still good to be used!
I see the this fastpack page recommends disabling the Executor Tagging sensor. However, the AppMon 6.5 documentation page on Cassandra integration states that "in order to be able to see Cassandra CQL3 protocol based statement execution, the Executor Tagging sensor needs to be active".
Does this sensor need to be enabled or disabled? (or is there no difference).