prometheus/jmx_exporter

A process for collecting metrics using JMX MBeans for Prometheus consumption

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 29 minutes ago
Added to GitGenius on September 20th, 2026
Created on February 25th, 2014
Open Issues & Pull Requests: 12 (+0)
GitHub issues: Enabled
Number of forks: 1,226
Total Stargazers: 3,329 (+0)
Total Subscribers: 70 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 11
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 653 days
Stale 30+ days: 10
Stale 90+ days: 8

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • status: closed due to inactivity (37)
  • theme: configuration (33)
  • status: resolved (23)
  • type: question (22)
  • status: waiting on feedback (19)
  • type: enhancement (19)
  • status: working as designed (10)
  • theme: third party issue (9)

Most active issues this week

Detailed Description

JMX Exporter is a Prometheus exporter that collects metrics from Java applications using JMX MBeans.

The tool solves the problem of exposing Java application metrics to Prometheus monitoring systems. Java applications expose internal metrics through JMX MBeans, but Prometheus requires metrics in its own text-based format. JMX Exporter bridges this gap by reading MBean attributes and converting them into Prometheus-compatible metrics that can be scraped by Prometheus servers. It operates as a Java agent that attaches to running JVM processes or as a standalone process that connects to remote JMX ports.

Teams should adopt JMX Exporter when monitoring Java applications with Prometheus and need access to JVM-level metrics and application-specific metrics exposed through MBeans. It suits any Java deployment where JMX is already enabled or can be enabled, from traditional application servers to microservices. The tool is particularly valuable for organizations already invested in Prometheus as their monitoring backend, as it provides native integration without requiring application code changes.

The project maintains active development with regular commits addressing bug fixes and feature enhancements. Pull requests receive timely review and feedback from maintainers. The codebase shows consistent attention to test coverage and code quality standards. Issue discussions demonstrate engagement with user questions and problem reports. The project follows a structured approach to releases with clear versioning practices.