JavaMelody 1.67.0 released

[Vernat Emeric]

JavaMelody 1.67.0 was released with a lot of new features, including Real User Monitoring. The release is available for download here:
https://github.com/javamelody/javamelody/releases

Release notes of 1.67.0:

• known major issue in 1.67.0, #634: Deployment error related to CDI in WebLogic and warnings in JBoss (fixed in master).
• fix #617: Charts of http/sql stats can not be viewed after restarting the application (with help from goldyliang).
• fix #622: In the collector server, malformed main html page when the monitored app is down.
• fix #623: In the collector server, spikes on gc, transaction and cpu graphs after collector restart.
• fix: In the collector server, after a restart, a monitored application can't be removed if it is no longer available.
• fix #631: When using the collector server, minor security issue if XML transport format with xstream is configured in the collector server parameters.
• fix: If the monitoring of an invalid JNDI datasource fails, don't ignore the others (dca0b07).
• added: When using Ehcache, display keys from the caches and add ability to remove a specific key from a cache (PR #630, thanks to Aleksandr Mashchenko).
• added: Display the number of http sessions and sessions mean size before the list of sessions, when there are more than 20 (PR #629, thanks to Aleksandr Mashchenko).
• improved: When displaying Java sources from stack-traces, locate more sources by reading Maven pom.xml of the webapp and of the other dependencies, when they exist.
• added: Display webapp dependencies in a new page, accessed by a link in the System informations details, and include detailed name, website url, Maven groupId:artifactId:version and license of each dependency, based on Maven pom.xml files. (e7607c1, except in JIRA/Confluence/Bamboo because of OSGi restrictions)
• added: With Spring, when using net/bull/javamelody/monitoring-spring.xml in the Spring context or when using the Spring boot starter, add a link to display "Spring beans", in System informations next to the "JNDI tree" link (5cd7c5a).
• added: With Spring again, when using net/bull/javamelody/monitoring-spring.xml in the Spring context or when using the Spring boot starter, if RestTemplate is used and if it is defined as Spring bean (for example, <bean id="restTemplate" class="org.springframework.web.client.RestTemplate" />), then the REST http calls from the webapp with this RestTemplate are monitored and response times are displayed in the Spring statistics of the monitoring report (b672ddb).
• added: In the database reports, 10 new reports for MySQL (with help from MySQL perf analyzer, Apache license): long running queries, statistics of tables, unused indexes, events waits summary, table access summary, index access summary, table lock wait summary, tables without PK, queries summary for the last 24h, memory summary (this last one works only in MySQL v5.7) and 1 new report for Oracle database: statistics of tables (62d86d1).
• added: When the webapp is built by Maven or when the javamelody parameter application-version is set, the version of the webapp is displayed at the top of the report and a drop-down list of versions next to "Customized" period allows to display the report for the period of each version deployed, to compare between them for example. (d61e65f, based on an idea by dhartford).
• added: Like for EJB monitoring, monitor CDI (or EJB 3.1) beans by simply adding the @net.bull.javamelody.Monitored annotation on beans classes or methods to monitor (3f60bff).
• added: Real User Monitoring (RUM). It allows to measure the experience from the end user perspective, by monitoring times in the browser for each html page until it is displayed and ready to be used (b85652a, see doc).
• The Real User Monitoring works by injecting on the fly a Boomerang javascript at the end of html pages, just before the </body> end tag, which sends data back to the monitoring in your server. Then in the detailed monitoring report of http requests for html pages, times and percentages are displayed for Network, Server execution, DOM processing and Page rendering, to compare which ones contribute to a good or bad end user experience. The Real User Monitoring does not add a noticeable overhead on the server, but the javascript adds a simple http(s) call for each html page, which may add a small overhead on the client browser.
• This Real User Monitoring is not enabled by default. To enable it, add a parameter rum-enabled in web.xml, in context or in system properties like the other javamelody parameters. For example in your WEB-INF/web.xml file:

	<filter>
		<filter-name>javamelody</filter-name>
		<filter-class>net.bull.javamelody.MonitoringFilter</filter-class>
		<init-param>
			<param-name>rum-enabled</param-name>
			<param-value>true</param-value>
		</init-param>
	</filter>
	...

• improved: when using the net.bull.javamelody.JdbcDriver in your configuration (without a datasource), accept the driver class in the jdbc URL like in the jdbc properties (617adff). For example in hibernate.cfg.xml:

<property name="hibernate.connection.driver_class">net.bull.javamelody.JdbcDriver</property>
<property name="hibernate.connection.url">jdbc:mysql://localhost:3306/myschema?driver=com.mysql.jdbc.Driver</property>

or

<property name="hibernate.connection.driver_class">net.bull.javamelody.JdbcDriver</property>
<property name="hibernate.connection.driver">com.mysql.jdbc.Driver</property>
<property name="hibernate.connection.url">jdbc:mysql://localhost:3306/myschema</property>

The Jenkins plugin, the JIRA, Confluence and Bamboo plugin, the Liferay plugin, the Alfresco plugin, the Sonar plugin and the Grails plugin were also released.
bye, Emeric