The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Sysmon
Posts with mentions or reviews of Sysmon.
We have used some of these posts to build our list of alternatives
and similar projects.
We haven't tracked posts mentioning Sysmon yet.
Tracking mentions began in Dec 2020.
jmxtrans
Posts with mentions or reviews of jmxtrans.
We have used some of these posts to build our list of alternatives
and similar projects.
-
Dissecting the CPU-Memory Relationship in Garbage Collection (OpenJDK 26)
I built this 15 years ago and it got fairly popular, but is long dead now...
https://github.com/jmxtrans/jmxtrans
Kind of amazing how people are still building telemetry into Java.
What are some alternatives?
When comparing Sysmon and jmxtrans you can also consider the following projects:
Automon - Automon combines the power of AOP (AspectJ) with monitoring or logging tools you already use to declaratively trace and monitor your Java code, the JDK, and 3rd party libraries.
Jolokia - JMX on Capsaicin
prometheus - The Prometheus monitoring system and time series database.
Metrics - :chart_with_upwards_trend: Capturing JVM- and application-level metrics. So you know what's going on.
nudge4j - Get inside your JVM