Java Application Monitor API
The Java Application Monitor (JAMon) is a free, simple, high performance, thread safe, Java API that allows developers to easily monitor production applications. JAMon can be used to determine application performance bottlenecks, user/application interactions, and application scalability. JAMon gathers summary statistics such as hits, execution times (total, average, minimum, maximum, standard deviation), and simultaneous application requests. JAMon statistics are displayed in the sortable JAMon report.
| Tags | Utilities Networking Monitoring Benchmark Software Development Testing Libraries Java Libraries Database Front-Ends Scientific/Engineering Office/Business Internet Web Dynamic Content Information Management |
|---|---|
| Licenses | BSD Revised |
| Operating Systems | OS Independent |
| Implementation | Java |
Recent releases
- 21 Aug 2011 14:02
Release Notes: This is a minor release. Concurrency was improved. A regression bug that broke EJB monitoring was fixed.
- 11 Aug 2011 13:18
Release Notes: This is a minor release. However, JDK 1.5 or higher is now required. Nanosecond timing is now available, which provides the ability to monitor anything on your OS such as your scripts.
- 24 Jul 2011 13:36
Release Notes: This is a minor release that adds a few features that users requested after version 2.7. JAMon still requires JDK 1.4 or higher (with a couple exceptions). If version 2.7 is working for you and you don't want the new features, then this is not a required upgrade.
- 20 Sep 2007 13:25
Release Notes: This release adds the ability to monitor Tomcat 4/5/5.5/6, JBoss 4.0.5, and Jetty 6.1.5 page resources. It adds an EJB3 interceptor that will monitor EJB calls and exceptions. Added to existing features, these allow developers to monitor servlets/JSPs, EJBs, JDBC/SQL, and log4j without requiring any code changes on their part.
- 03 Jun 2007 13:53
Release Notes: This release adds a JAMon log4j Appender that will allow developers to keep aggregate statistics on log4j messages. For example, they will be able to use a JAMon Web page to view how many errors have been sent to log4j. They will also be able to 'tail' the log4j log file via a JAMon Web page. All of this can be configured via the log4j XML or properties configurator. No code changes are required in your application.
Heartbeat
- Popularity Score
- 143.27
- Vitality Score
- 11.87
- Subscriptions
- 32
