Hello !
I'm currently trying to retrieve JVM metrics through Jolokia and Metricbeat but i'm facing an issue. When Metricbeat (on server 1) calls Jolokia agents (on server 2) over the network i get 403 HTTP response. But if i install metricbeat on server 1 and use the same configuration (except that hosts are changed), it works like a charm.
Here is the error received :
{
"log.level": "error",
"@timestamp": "2025-02-10T12:03:52.382+0100",
"log.origin": {
"function": "[github.com/elastic/beats/v7/metricbeat/mb/module.(*metricSetWrapper).handleFetchError](http://github.com/elastic/beats/v7/metricbeat/mb/module.%28*metricSetWrapper%29.handleFetchError)",
"[file.name](http://file.name)": "module/wrapper.go",
"file.line": 333
},
"message": "Error fetching data for metricset jolokia.jmx: HTTP error 403 in : 403 Forbidden",
"[service.name](http://service.name)": "metricbeat",
"ecs.version": "1.6.0"
}
Jolokia agents have no authentication configured. No SSL configuration neither.
So i don't understand why i have this issue. Can you help to understand and fix this ?
Here is the configuration of Metricbeat and jolokia plugin (module metricbeat)
metricbeat.yml
###################### Metricbeat Configuration Example #######################
# This file is an example configuration file highlighting only the most common
# options. The metricbeat.reference.yml file from the same directory contains all the
# supported options with more comments. You can use it as a reference.
#
# You can find the full configuration reference here:
# https://www.elastic.co/guide/en/beats/metricbeat/index.html
# =========================== Modules configuration ============================
metricbeat.config.modules:
# Glob pattern for configuration loading
path: ${path.config}/modules.d/*.yml
# Set to true to enable config reloading
reload.enabled: false
# Period on which files under path should be checked for changes
#reload.period: 10s
# ======================= Elasticsearch template setting =======================
setup.template.settings:
index.number_of_shards: 1
index.codec: best_compression
#_source.enabled: false
# ================================== General ===================================
# The name of the shipper that publishes the network data. It can be used to group
# all the transactions sent by a single shipper in the web interface.
#name:
# The tags of the shipper are included in their field with each
# transaction published.
#tags: ["service-X", "web-tier"]
# Optional fields that you can specify to add additional information to the
# output.
#fields:
# env: staging
# ================================= Dashboards =================================
# These settings control loading the sample dashboards to the Kibana index. Loading
# the dashboards is disabled by default and can be enabled either by setting the
# options here or by using the `setup` command.
#setup.dashboards.enabled: false
# The URL from where to download the dashboard archive. By default, this URL
# has a value that is computed based on the Beat name and version. For released
# versions, this URL points to the dashboard archive on the artifacts.elastic.co
# website.
#setup.dashboards.url:
# =================================== Kibana ===================================
# Starting with Beats version 6.0.0, the dashboards are loaded via the Kibana API.
# This requires a Kibana endpoint configuration.
#setup.kibana:
# Kibana Host
# Scheme and port can be left out and will be set to the default (http and 5601)
# In case you specify and additional path, the scheme is required: http://localhost:5601/path
# IPv6 addresses should always be defined as: https://[2001:db8::1]:5601
#host: "localhost:5601"
# Kibana Space ID
# ID of the Kibana Space into which the dashboards should be loaded. By default,
# the Default Space will be used.
#space.id:
# =============================== Elastic Cloud ================================
# These settings simplify using Metricbeat with the Elastic Cloud (https://cloud.elastic.co/).
# The cloud.id setting overwrites the `output.elasticsearch.hosts` and
# `setup.kibana.host` options.
# You can find the `cloud.id` in the Elastic Cloud web UI.
#cloud.id:
# The cloud.auth setting overwrites the `output.elasticsearch.username` and
# `output.elasticsearch.password` settings. The format is `<user>:<pass>`.
#cloud.auth:
# ================================== Outputs ===================================
# Configure what output to use when sending the data collected by the beat.
# ---------------------------- Elasticsearch Output ----------------------------
#output.elasticsearch:
# Array of hosts to connect to.
#hosts: ["localhost:9200"]
# Performance preset - one of "balanced", "throughput", "scale",
# "latency", or "custom".
#preset: balanced
# Protocol - either `http` (default) or `https`.
#protocol: "https"
# Authentication credentials - either API key or username/password.
#api_key: "id:api_key"
#username: "elastic"
#password: "changeme"
# ------------------------------ Logstash Output -------------------------------
output.logstash:
# The Logstash hosts
hosts: ["XXX.XXX.XXX.XXX:XXXXXX"]
# Optional SSL. By default is off.
# List of root certificates for HTTPS server verifications
#ssl.certificate_authorities: ["/etc/pki/root/ca.pem"]
# Certificate for SSL client authentication
#ssl.certificate: "/etc/pki/client/cert.pem"
# Client Certificate Key
#ssl.key: "/etc/pki/client/cert.key"
# ================================= Processors =================================
# Configure processors to enhance or manipulate events generated by the beat.
processors:
# - add_host_metadata: ~
# - add_cloud_metadata: ~
# - add_docker_metadata: ~
# - add_kubernetes_metadata: ~
# - add_process_metadata: ~
# ================================== Logging ===================================
# Sets log level. The default log level is info.
# Available log levels are: error, warning, info, debug
#logging.level: debug
# At debug level, you can selectively enable logging only for some components.
# To enable all selectors, use ["*"]. Examples of other selectors are "beat",
# "publisher", "service".
#logging.selectors: ["*"]
logging.metrics.enabled: false
# ============================= X-Pack Monitoring ==============================
# Metricbeat can export internal metrics to a central Elasticsearch monitoring
# cluster. This requires xpack monitoring to be enabled in Elasticsearch. The
# reporting is disabled by default.
# Set to true to enable the monitoring reporter.
#monitoring.enabled: false
# Sets the UUID of the Elasticsearch cluster under which monitoring data for this
# Metricbeat instance will appear in the Stack Monitoring UI. If output.elasticsearch
# is enabled, the UUID is derived from the Elasticsearch cluster referenced by output.elasticsearch.
#monitoring.cluster_uuid:
# Uncomment to send the metrics to Elasticsearch. Most settings from the
# Elasticsearch outputs are accepted here as well.
# Note that the settings should point to your Elasticsearch *monitoring* cluster.
# Any setting that is not set is automatically inherited from the Elasticsearch
# output configuration, so if you have the Elasticsearch output configured such
# that it is pointing to your Elasticsearch monitoring cluster, you can simply
# uncomment the following line.
#monitoring.elasticsearch:
# ============================== Instrumentation ===============================
# Instrumentation support for the metricbeat.
#instrumentation:
# Set to true to enable instrumentation of metricbeat.
#enabled: false
# Environment in which metricbeat is running on (eg: staging, production, etc.)
#environment: ""
# APM Server hosts to report instrumentation results to.
#hosts:
# - http://localhost:8200
# API Key for the APM Server(s).
# If api_key is set then secret_token will be ignored.
#api_key:
# Secret token for the APM Server(s).
#secret_token:
# ================================= Migration ==================================
# This allows to enable 6.7 migration aliases
#migration.6_to_7.enabled: true
Jolokia plugin configuration :
# Module: jolokia
# Docs: https://www.elastic.co/guide/en/beats/metricbeat/8.x/metricbeat-module-jolokia.html
- module: jolokia
metricsets: ["jmx"]
period: 60s
hosts: [
"XXXXXXXXX:4242",
"XXXXXXXXX:4243",
"XXXXXXXXX:4244",
"XXXXXXXXX:4245",
"XXXXXXXXX:4246",
"XXXXXXXXX:4247",
"XXXXXXXXX:4248",
"XXXXXXXXX:4249"
]
namespace: "metrics"
path: "/jolokia/read/"
#username: "user"
#password: "secret"
jmx.mappings:
- mbean: 'java.lang:type=Memory'
attributes:
- attr: HeapMemoryUsage
field: memory.heap_usage
- mbean: 'java.lang:type=Threading'
attributes:
- attr: ThreadCount
field: threads.count
- mbean: 'java.lang:type=OperatingSystem'
attributes:
- attr: ProcessCpuLoad
field: os.processCpuLoad
- mbean: 'java.lang:type=GarbageCollector,name=G1 Young Generation'
attributes:
- attr: CollectionCount
field: gc.young.collectionCount
- attr: CollectionTime
field: gc.young.collectionTime
- attr: LastGcInfo
field: gc.young.lastGcInfo
- mbean: 'java.lang:type=GarbageCollector,name=G1 Old Generation'
attributes:
- attr: CollectionCount
field: gc.old.collectionCount
- attr: CollectionTime
field: gc.old.collectionTime
- attr: LastGcInfo
field: gc.old.lastGcInfo
- mbean: 'java.nio:type=BufferPool,name=direct'
attributes:
- attr: MemoryUsed
field: nio.direct.memoryUsed
- attr: Count
field: nio.direct.count
- mbean: 'java.nio:type=BufferPool,name=mapped'
attributes:
- attr: MemoryUsed
field: nio.mapped.memoryUsed
- attr: Count
field: nio.mapped.count
- mbean: 'java.lang:type=Runtime'
attributes:
- attr: Name
field: runtime.name
- attr: InputArguments
field: runtime.inputArgs
- attr: Pid
field: runtime.pid
jmx.application:
jmx.instance:
Thanks you !
Regards,
Nso