From 09173673c3856336c807efd180a3214a7b78084e Mon Sep 17 00:00:00 2001 From: Anna Urbiztondo Date: Wed, 25 Sep 2024 12:15:37 +0200 Subject: [PATCH 1/2] Cassandra --- gdi/opentelemetry/components/jmx-receiver.rst | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-) diff --git a/gdi/opentelemetry/components/jmx-receiver.rst b/gdi/opentelemetry/components/jmx-receiver.rst index 40dd504e8..a4f2a2974 100644 --- a/gdi/opentelemetry/components/jmx-receiver.rst +++ b/gdi/opentelemetry/components/jmx-receiver.rst @@ -9,9 +9,14 @@ JMX receiver The JMX receiver works in conjunction with the :new-page:`OpenTelemetry JMX Metric Gatherer ` to report metrics from an MBean server. The supported pipeline type is ``metrics``. See :ref:`otel-data-processing` for more information. +You can use the JMX receiver to monitor services such as Cassandra using the ``target_system`` setting. See more at :ref:`jmx-receiver-advanced` and :ref:`jmx-receiver-settings`. + .. note:: Out-of-the-box dashboards and navigators aren't supported for the JMX receiver yet, but are planned for a future release. -This receiver launches a child JRE process which runs the JMX Metric Gatherer configured with your specified JMX connection information and target built-in OTel-helper Groovy script. It then reports metrics to an implicitly created OTLP receiver. +Prerequisites +====================== + +The receiver launches a child JRE process which runs the JMX Metric Gatherer configured with your specified JMX connection information and target built-in OTel-helper Groovy script. It then reports metrics to an implicitly created OTLP receiver. In order to use the JMX receiver: @@ -77,7 +82,9 @@ This examples provides configuration details for the receiver: log_level: info additional_jars: - /path/to/other.jar - + +.. _jmx-receiver-advanced: + Advanced settings ----------------------------------------------- @@ -98,7 +105,7 @@ You can use the following advanced settings with the receiver: * ``target_system``. The built-in target system (or systems) metric gatherer script to run. - * Must be a subset of: ``"activemq"``, ``"cassandra"``, ``"hbase"``, ``"hadoop"``, ``"jetty"``, ``"jvm"``, ``"kafka"``, ``"kafka-consumer"``, ``"kafka-producer"``, ``"solr"``, ``"tomcat"``, or ``"wildfly"``. + * Possible values: ``"activemq"``, ``"cassandra"``, ``"hbase"``, ``"hadoop"``, ``"jetty"``, ``"jvm"``, ``"kafka"``, ``"kafka-consumer"``, ``"kafka-producer"``, ``"solr"``, ``"tomcat"``, or ``"wildfly"``. * If you need to support additional target systems because of a custom JMX metrics gatherer jar configured using the ``MetricsGathererHash`` build time config, add them with another build time flag. It corresponds to the ``otel.jmx.target.system`` property. From 6457795e6d63e2753aa30e341ad391fa6342ba00 Mon Sep 17 00:00:00 2001 From: Anna Urbiztondo Date: Sun, 29 Sep 2024 17:22:59 +0200 Subject: [PATCH 2/2] Feedback --- gdi/opentelemetry/components/jmx-receiver.rst | 2 ++ 1 file changed, 2 insertions(+) diff --git a/gdi/opentelemetry/components/jmx-receiver.rst b/gdi/opentelemetry/components/jmx-receiver.rst index a4f2a2974..1a42f243e 100644 --- a/gdi/opentelemetry/components/jmx-receiver.rst +++ b/gdi/opentelemetry/components/jmx-receiver.rst @@ -106,6 +106,8 @@ You can use the following advanced settings with the receiver: * ``target_system``. The built-in target system (or systems) metric gatherer script to run. * Possible values: ``"activemq"``, ``"cassandra"``, ``"hbase"``, ``"hadoop"``, ``"jetty"``, ``"jvm"``, ``"kafka"``, ``"kafka-consumer"``, ``"kafka-producer"``, ``"solr"``, ``"tomcat"``, or ``"wildfly"``. + + * You can specify multiple target systems at the same time: ``"target_system": "activemq, kafka,kafka-consumer"``. * If you need to support additional target systems because of a custom JMX metrics gatherer jar configured using the ``MetricsGathererHash`` build time config, add them with another build time flag. It corresponds to the ``otel.jmx.target.system`` property.