Hadoop JMX π
The Splunk Distribution of OpenTelemetry Collector uses the Smart Agent receiver with the Hadoop JMX monitor type to collect metrics from Hadoop 2.0 or higher clusters.
This integration produces metrics from a set of built-in MBeans
available for the respective nodeTypes
:
Name Nodes (
nameNode
)Resource Manager (
resourceManager
)Node Manager (
nodeManager
)Data Nodes (
dataNode
)
This integration uses the collectd GenericJMX plugin. You can also
configure the hadoop
monitor to collect additional metrics about the
Hadoop cluster using the REST API.
This integration is only available on Kubernetes and Linux.
Benefits π
After you configure the integration, you can access these features:
View metrics. You can create your own custom dashboards, and most monitors provide built-in dashboards as well. For information about dashboards, see View dashboards in Splunk Observability Cloud.
View a data-driven visualization of the physical servers, virtual machines, AWS instances, and other resources in your environment that are visible to Infrastructure Monitoring. For information about navigators, see Use navigators in Splunk Infrastructure Monitoring.
Access the Metric Finder and search for metrics sent by the monitor. For information, see Search the Metric Finder and Metadata catalog.
Requirements π
To activate JMX in Hadoop, add the following Java Virtual Machine (JVM) options to hadoop-env.sh and yarn-env.sh:
hadoop-env.sh:
export HADOOP_NAMENODE_OPTS="-Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.port=5677 $HADOOP_NAMENODE_OPTS"
export HADOOP_DATANODE_OPTS="-Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.port=5679 $HADOOP_DATANODE_OPTS"
yarn-env.sh:
export YARN_NODEMANAGER_OPTS="-Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.port=8002 $YARN_NODEMANAGER_OPTS"
export YARN_RESOURCEMANAGER_OPTS="-Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.port=5680 $YARN_RESOURCEMANAGER_OPTS"
Installation π
Follow these steps to deploy this integration:
Deploy the Splunk Distribution of OpenTelemetry Collector to your host or container platform:
Configure the monitor, as described in the Configuration section.
Restart the Splunk Distribution of OpenTelemetry Collector.
Configuration π
To use this integration of a Smart Agent monitor with the Collector:
Include the Smart Agent receiver in your configuration file.
Add the monitor type to the Collector configuration, both in the receiver and pipelines sections.
See how to Use Smart Agent monitors with the Collector.
See how to set up the Smart Agent receiver.
For a list of common configuration options, refer to Common configuration settings for monitors.
Learn more about the Collector at Get started: Understand and use the Collector.
Example π
To activate this integration, add the following to your Collector configuration:
receivers:
smartagent/collectd/hadoopjmx:
type: collectd/hadoopjmx
... # Additional config
Next, add the monitor to the service.pipelines.metrics.receivers
section of your configuration file:
service:
pipelines:
metrics:
monitors: [smartagent/collectd/hadoopjmx]
Sample configuration for nodeTypes π
The following sample configurations show how to configure the monitor for different nodeTypes.
Name Node:
receivers:
smartagent/collectd/hadoopjmx:
type: collectd/hadoopjmx
host: 127.0.0.1
port: 5677
nodeType: nameNode
Resource Manager:
receivers:
smartagent/collectd/hadoopjmx:
type: collectd/hadoopjmx
host: 127.0.0.1
port: 5680
nodeType: resourceManager
Node Manager:
receivers:
smartagent/collectd/hadoopjmx:
type: collectd/hadoopjmx
host: 127.0.0.1
port: 8002
nodeType: nodeManager
Data Node:
receivers:
smartagent/collectd/hadoopjmx:
type: collectd/hadoopjmx
host: 127.0.0.1
port: 5679
nodeType: dataNode
Configuration options π
The following table shows the configuration options for the collectd/hadoopjmx receiver:
Option |
Required |
Type |
Description |
---|---|---|---|
|
yes |
|
|
|
yes |
|
|
|
no |
|
|
|
no |
|
|
|
no |
|
|
|
no |
|
|
|
no |
|
Username to authenticate to the server. |
|
no |
|
User password to authenticate to the server. |
|
no |
|
|
|
no |
|
|
|
no |
|
|
|
no |
|
|
|
yes |
|
Hadoop nodeType. |
The nested mBeanDefinitions
configuration object has the following
fields:
Option |
Required |
Type |
Description |
---|---|---|---|
|
no |
|
|
|
no |
|
Prefixes the generated plugin instance with a prefix. |
|
no |
|
|
|
no |
|
|
|
no |
|
A list of strings for the dimensions. |
The nested values
config object has the following fields:
Option |
Required |
Type |
Description |
---|---|---|---|
|
no |
|
|
|
no |
|
|
|
no |
|
|
|
no |
|
|
|
no |
|
|
|
no |
|
|
Metrics π
The following metrics are available for this integration:
Notes π
To learn more about the available in Splunk Observability Cloud see Metric types
In host-based subscription plans, default metrics are those metrics included in host-based subscriptions in Splunk Observability Cloud, such as host, container, or bundled metrics. Custom metrics are not provided by default and might be subject to charges. See Metric categories for more information.
In MTS-based subscription plans, all metrics are custom.
To add additional metrics, see how to configure
extraMetrics
in Add additional metrics
Troubleshooting π
If you are a Splunk Observability Cloud customer and are not able to see your data in Splunk Observability Cloud, you can get help in the following ways.
Available to Splunk Observability Cloud customers
Submit a case in the Splunk Support Portal .
Contact Splunk Support .
Available to prospective customers and free trial users
Ask a question and get answers through community support at Splunk Answers .
Join the Splunk #observability user group Slack channel to communicate with customers, partners, and Splunk employees worldwide. To join, see Chat groups in the Get Started with Splunk Community manual.