| Date | News |
|---|---|
| 22 April 2005 | JDiagnose 2.0 Beta 3 has been released. New features include: importing results, duration chart, querying historical results, a web trail, a dropdown to switch systems (e.g. between a queried system and the current system) and various bug fixes |
| 10 March 2005 | JDiagnose 2.0 Beta 2 has been released. New features include: recent results on the home page, success/failure stacked bar chart, csv logging, manual results and a move to velocity. Bug fixes include: HttpSender now sends the sequenceNumber, various synchronization updates etc. |
| 4 March 2005 | JDiagnose 2.0 Beta1.1 has been released. This is a patch release to fix some issues that Chico Charlesworth kindly pointed out. |
| 3 March 2005 | JDiagnose 2.0 Beta1 has been released. Check out the screenshots below or head off to SourceForge, download it and try it out. Note, Beta1 is configured to use a MockRemoteSystem by default (for testing with 100 000 diagnostic results). To use it for your own diagnostics, change the bean reference "mockRemoteSystem" to "inMemoryRemoteSystem" in WEB-INF/classes/diagnostics.xml. |
JDiagnose is a Java toolset intended to assist in diagnosing and monitoring live systems. To get an idea, here are a few screenshots of the JDiagnose Server application:
 | JDiagnose home page. Lists the latest diagnostic results. |
 | Stacked Bar Chart showing numbers of successful and failed diagnostics over a period. |
 | List of all the Agents being monitored. An agent represents a single application that has been deployed on one or more hosts. Red (or maybe rouge) rows indicate agents that have failing diagnostics on a particular host. |
 | A list of all the hosts a particular Agent is running on. JDiagnose supports starting browsing either by Agent first and then the hosts it's running on, or by Host and all the agents that are running on it. |
 | Diagnostics for an Agent on a particular host. Diagnostics can either be independent entities, e.g. testing a database connection every five minutes, or can be the result of instrumented existing method calls. |
 | Historical results for a particular Diagnostic. |
 | Detail view of the result of a single diagnostic run or method call |
 | Chart of historical diagnostic timings. |
 | A Diagnostics runner. |