Merge pull request #2274 from splunk/urbiz-OD6394-note-jmx

[6394]: JMX notes

Author: aurbiztondo-splunk

gdi/monitors-languages/genericjmx.rst

@@ -6,12 +6,10 @@ GenericJMX
 .. meta::
    :description: Use this Splunk Observability Cloud integration for the GenericJMX monitor. See benefits, install, configuration, and metrics
 
-The Splunk Distribution of OpenTelemetry Collector uses the Smart Agent receiver with the
-``genericjmx`` monitor to expose metrics on Java Management Extensions
-(JMX), a generic framework to provide and query management information.
-The interface is used by the Java Virtual Machine (JVM) to provide
-information about the memory used and threads. For a more flexible
-alternative, use :ref:`the JMX monitor <genericjmx>`
+The Splunk Distribution of the OpenTelemetry Collector uses the Smart Agent receiver with the ``genericjmx`` monitor to expose metrics on Java Management Extensions (JMX), a generic framework to provide and query management information. The interface is used by the Java Virtual Machine (JVM) to provide
+information about the memory used and threads. For a more flexible alternative, use :ref:`the JMX monitor <genericjmx>`.
+
+.. note:: To monitor JMX with the OpenTelemetry Collector using native OpenTelemetry components refer to the :ref:`jmx-receiver`.
 
 This integration is only available on Kubernetes and Linux.
 

gdi/monitors-languages/jmx.rst

@@ -6,16 +6,15 @@ JMX
 .. meta::
    :description: Use this Splunk Observability Cloud integration for the JMX monitor. See benefits, install, configuration, and metrics. Run an arbitrary Groovy script to convert JMX MBeans fetched from a remote Java application to SignalFx data points
 
-The Splunk Distribution of OpenTelemetry Collector uses the Smart Agent receiver with the
-``jmx`` monitor type to run an arbitrary Groovy script to convert JMX
-MBeans fetched from a remote Java application to SignalFx data points.
-This is a more flexible alternative to the
-:ref:`GenericJMX <genericjmx>` monitor.
+The Splunk Distribution of the OpenTelemetry Collector uses the Smart Agent receiver with the ``jmx`` monitor type to run an arbitrary Groovy script to convert JMX MBeans fetched from a remote Java application to SignalFx data points. This is a more flexible alternative to the :ref:`GenericJMX <genericjmx>` monitor.
 
-.. note:: If you are instrumenting an application with the Splunk Distribution of OpenTelemetry Java, you can capture metrics with the Java agent instead of using a JMX monitor. To learn more, see :ref:`enable_automatic_metric_collection`
+.. note:: 
+   
+   To monitor JMX with the OpenTelemetry Collector using native OpenTelemetry components refer to the :ref:`jmx-receiver`.
 
-You can use the following utility helpers in the Groovy script within
-the ``util`` variable, which is set in the script's context:
+   If you are instrumenting an application with the Splunk Distribution of OpenTelemetry Java, you can capture metrics with the Java agent instead of using a JMX monitor. To learn more, see :ref:`enable_automatic_metric_collection`.
+
+You can use the following utility helpers in the Groovy script within the ``util`` variable, which is set in the script's context:
 
 -  ``util.queryJMX(String objectName)``: This helper queries the
    configured JMX application for the given ``objectName``, which can

gdi/opentelemetry/components/jmx-receiver.rst

@@ -9,12 +9,14 @@ JMX receiver
 
 The JMX receiver works in conjunction with the :new-page:`OpenTelemetry JMX Metric Gatherer <https://github.com/open-telemetry/opentelemetry-java-contrib/blob/main/jmx-metrics/README.md>` to report metrics from an MBean server. The supported pipeline type is ``metrics``. See :ref:`otel-data-processing` for more information.
 
+.. note:: Out-of-the-box dashboards and navigators aren't supported for the Apache Web Server 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. 
 
 In order to use the JMX receiver:
 
-* Download the most recent release of the JMX Metric Gatherer JAR and configure the receiver with its path. 
-* JRE must be available on your system.
+* Download the most recent release of the JMX Metric Gatherer JAR and configure the receiver with its path 
+* JRE must be available on your system
 
 Get started
 ======================