monitoring-1.99.0

• Updated Chinese (continental) translations (9ecde16, thanks to an unnamed user)
• To contribute in your own language, join the translation project at https://poeditor.com/join/project/QIaCp4bThS.

monitoring-1.98.0

Upgrades to test with Java 21 (PR #12 thanks to Basil, MarkEWaite, Kohsuke)

monitoring-1.95.0

• Fix #1165 Latest IBM J9 JVM: MBeansAccessor.getThreadAllocatedBytes throws UnsupportedOperationException
• When publishing metrics to InfluxDB and if you prefer an api token instead of basic authentication in the InfluxDB server, the api token can be set with the -Djavamelody.influxdb-api-token=... system property. Basic authentication is still supported, including with InfluxDB 2.x #1170

monitoring-1.94.1

• fix JENKINS-70279 404 errors for links in the node's monitoring page.
• fix JENKINS-69785 The "build queue length" graph of the monitoring agents page now counts all items including blocked items, instead of just buildable items.
• Use "Jenkins instance" instead of "Jenkins master" (thanks to Thierry Wasylczenko).

monitoring-1.94.0

• fix IllegalStateException & ClassCastException when reading corrupted statistics (gz) files (PR 1144, thanks to alireza-kasraei).

monitoring-1.92.0

• Improve word wrap for ultra long requests (PR 1100, thanks to Roland Praml).

monitoring-1.91.0

• fix JENKINS-66855 Periodic LinkageError / NoClassDefFoundError in Jenkins node

monitoring-1.90.0

• upgrade Log4j 2 in the optional javamelody collect server for CVE-2021-45046.

monitoring-1.89.0

• upgrade Log4j 2 in the optional javamelody collect server for CVE-2021-44228.
• fix #933 Http sessions with changed ids are removed from sessions page when one of them terminates (PR 934, thanks to lmalmeida)

monitoring-1.88.0

• added support for Eclipse OpenJ9 JVM heap dump #1024
• externalize some css and js (based on PR 966, thanks to Craig Andrews)
• work towards Content-Security-Policy (PR 1006, PR 1007, PR 1008, PR 1009, PR 1030 based on PR 966 thanks to Craig Andrews + fixes)
• added to enhance security, Content-Security-Policy is now enabled by default in the monitoring page. The parameter content-security-policy-enabled can be set to false to disable it. (PR 1031 thanks to Craig Andrews)
• updated Chinese traditional (Taïwan) translations, (language "zh-TW", ac883fa, thanks to Jack)