Hi ASK45, Did you find a solution for this? Looking for the same thing. From what I have understood till now I think a standalone cassandra exporter has to be used if you are not willing to makes changes to your cassandra-env.sh. Do let me know if you find any solution for monitoring cassandra using JMX Exporter without adding it to the cassandra-env.sh.
On Sunday, June 14, 2020 at 12:42:50 AM UTC+5:30 ASK45 wrote: > java > -javaagent:/opt/jmx_prometheus/jmx_prometheus_javaagent-0.13.0.jar=7070:/opt/jmx_prometheus/6.yaml > > -jar **/opt/jmx_prometheus/jmx_prometheus_javaagent-0.13.0.jar > > no main manifest attribute, in > /opt/jmx_prometheus/jmx_prometheus_javaagent-0.13.0.jar > > > what should -jar be for monitoring cassandra with a separate agent demon > for Prometheus ? > > > java -javaagent:./jmx_prometheus_javaagent-0.13.0.jar=8080:config.yaml > -jar *yourJar.jar* > > > what should *yourJar.jar* be for monitoring Cassandra? > > I am trying to run jmx_eporter as a separate process/java agent instead of > adding it to cassandra-env.sh, has anyone done this before? > -- You received this message because you are subscribed to the Google Groups "Prometheus Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/686a1762-f322-4526-b68a-cb9b080e9938n%40googlegroups.com.
