Re: Cassandra JMX without RMI?
Hello, I haven't found any good documentation to refer to, but you can have a look at the following: https://github.com/apache/cassandra-sidecar https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=95652224 The sidecar is deployed alongside the Cassandra node and exposes metrics/commands via HTTP/REST. This is what it look like: https://cwiki.apache.org/confluence/download/attachments/247827919/SBW%20OSS%20SBR.jpg?version=1&modificationDate=1681166031000&api=v2 On Wed, 19 Jul 2023 at 19:00, Angelo Polo wrote: > > Thanks Max, that's a good option to know about. > > Unfortunately I have a fairly strict requirement for an agentless > architecture. It's possible to have some values set in cassandra-env for > example, but I can't say "download and install this jar here" (Jalokia agent > mode) or "run this code from here" (Jalokia proxy mode - Jalokia would still > be using JMX over RMI I assume, but the proxy shields my application from > having to make RMI calls directly). > > Is JMX over RMI the only out-of-the-box way to communicate remotely with > Cassandra's MBean server? > > Best, > Angelo > > On Tue, Jul 18, 2023 at 11:49 PM Max Campos wrote: >> >> We use Jolokia. It runs inside of Cassandra and then gives you an HTTP REST >> interface to interact with JMX. Works great for us! >> >> https://jolokia.org/ >> >> - Max >> >> On Jul 18, 2023, at 8:11 pm, Angelo Polo wrote: >> >> Is it possible to connect to the Cassandra JMX server without using the RMI >> protocol? >> >> I have found for example, this open source project >> https://github.com/willemsrb/simple-jmx that claims to provide JMX without >> RMI, but it seems to need to be set up on the server side too, and of course >> Cassandra's JMX server isn't based on this project. >> >> So is there a client-side-only possibility to use something other than RMI >> when retrieving Cassandra JMX? >> >> Thanks, >> Angelo >> >>
[DISCUSSION] Removal of metrics-reporter-config in the next 5.0 release. Feedback needed
Dear Cassandra users, Some feedback is needed from your side, as the change itself is related to the way the internal metrics can be exported from the Cassandra node. If you are not using the metrics-reporter-config [1] and exporting metrics to the physical file provided by it, no action is required from your side. Please, note that this library is not related to the dropwizard metrics library, everything related to the latter library remains the same. We are trying to clean up obsolete dependencies, that are no longer in use and make the next upcoming 5.0 release safer from all perspectives. Currently, Cassandra provides a pluggable metrics reporter called metrics-reporter-config to export internal metrics, mostly reflected in JMX Beans, to a file, and this functionality is configured using the Cassandra.metricsReporterConfigFile system property which points to the metrics-reporter configuration file. The way that metrics can be exported is fully covered by the dropwizard metrics library itself, using e.g. CsvReporter [2], which has been a part of Cassandra for a long time, and, in fact, the metrics-reporter-config [1], which has been in the archive for almost 3 years, was not deprecated earlier in Cassandra 4.x only because of lack of attention to it. We want to fix this and remove the dependency on metrics-reporter-config library [1] support starting with the 5.0 release. Please let me know if the following removal affects you in any way by replying to this message or by posting to the related JIRA issue [3]. In addition, we want to get rid of the commons-codec dependency [4] that was used to put metrics reported by the metrics-reporter-config into the InfluxDB. If you have any concerns/questions, please let me know. [1] https://github.com/addthis/metrics-reporter-config [2] https://metrics.dropwizard.io/4.2.0/getting-started.html#other-reporting [3] https://issues.apache.org/jira/browse/CASSANDRA-18743 [4] https://issues.apache.org/jira/browse/CASSANDRA-18772
