SaaSHub helps you find the best software and product alternatives Learn more →
Jmx_exporter Alternatives
Similar projects and alternatives to jmx_exporter
-
-
AppSignal
AppSignal knows why the f*#k it crashed. Stop vibe-debugging. Every exception, every backtrace, grouped so you see patterns, not noise.
-
Telegraf
Agent for collecting, processing, aggregating, and writing metrics, logs, and other arbitrary data.
-
-
-
-
-
akhq
Kafka GUI for Apache Kafka to manage topics, topics data, consumers group, schema registry, connect and more...
-
Kargo
Stop Scripting Promotions. Start Shipping with Kargo. Kargo automates promotion across dev, staging, and prod with approval gates and verification. Open source, built by the team behind Argo CD. Download now.
-
-
-
-
-
-
-
-
-
-
-
kinesis-kafka-connector
kinesis-kafka-connector is connector based on Kafka Connect to publish messages to Amazon Kinesis streams or Amazon Kinesis Firehose.
-
pubsub
This repository contains open-source projects managed by the owners of Google Cloud Pub/Sub. (by GoogleCloudPlatform)
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
jmx_exporter discussion
jmx_exporter reviews and mentions
-
Learning Fullstack Observability: Metrics
OpenTelemetry Java Agent: for the backend. I could have also used Spring Actuator or the JMX exporter, but the agent is simpler for this project since it emits all 3 types of telemetry signals.
-
Prometheus JMX Exporter for Java17
not quite sure if this is where I should be asking for help but i'm kind of befuddled about this whole situation. I'm trying to set up https://github.com/prometheus/jmx_exporter for our containerized Java application on our cluster. Specifically the JavaAgent as we are interested in getting the CPU and memory metrics especially. However, getting it initialized I am faced with this:
-
Initial setup
Prometheus doesn't deal with logs at all - only metrics. Even just for metrics, you have several different choices depending on how your Java application is running. You may be able to use the JMX Exporter to expose the metrics that you would then scrape with Prometheus. For the logs, you'll need something like Fluent Bit as an agent to grab ('tail' in Fluent Bit input terms) the logs and send them to Elasticsearch or Grafana Loki.
- Pod log monitoring
- Monitor Java application with prometheus
-
What kind of monitoring tools are people using for their Kafka Deployment?
- https://github.com/prometheus/jmx_exporter - https://github.com/lightbend/kafka-lag-exporter (Export Kafka Topics Lag Metrics) - https://github.com/danielqsj/kafka_exporter (Export Kafka Metrics) - https://github.com/obsidiandynamics/kafdrop (Topic Administration tool - create/edit/delete topics & view messages)
-
Kafka monitoring
Usually I use a javaagent that transforms the JMX metrics into prometheus style metrics, for example: https://github.com/prometheus/jmx_exporter/blob/116a1c4b3fafcfbb9e566b34e130ccc805f331fc/example_configs/kafka-0-8-2.yml
-
Do you use Tomcat ? How to you get optimal performance of it?
Another good one is to add the jmx_exporter agent plugin. This allows easy collection of real-time performance metrics.
-
Kafka Connect: The Magic Behind Mux Data Realtime Exports
In our case, we add sink connectors for AWS Kinesis and Google Cloud PubSub. We also add a Prometheus exporter JAR that scrapes the Kafka Connect JMX metrics and exposes them as Prometheus metrics.
-
A note from our sponsor - SaaSHub
www.saashub.com | 7 Sep 2026
Stats
prometheus/jmx_exporter is an open source project licensed under Apache License 2.0 which is an OSI approved license.
The primary programming language of jmx_exporter is Java.
Popular Comparisons
- jmx_exporter VS example.java.helloworld
- jmx_exporter VS byblos
- jmx_exporter VS opentelemetry-java-contrib
- jmx_exporter VS kafka_exporter
- jmx_exporter VS kafka-lag-exporter
- jmx_exporter VS container-jfr
- jmx_exporter VS akhq
- jmx_exporter VS opentelemetry-java
- jmx_exporter VS kinesis-kafka-connector
- jmx_exporter VS client_java