cuba-platform / cuba-jm Goto Github PK

View Code? Open in Web Editor NEW

4.0 23.0 3.0 242 KB

CUBA app component that brings JavaMelody monitoring functionality

License: Apache License 2.0

Java 100.00%

cuba-component cuba-platform javamelody monitoring

cuba-jm's People

Contributors

Stargazers

Watchers

Forkers

kartndev russianbear36 kxb-pro

cuba-jm's Issues

metadata.xml should not be in the root package

the metadata.xml of the add-on may clash against metadata.xml of the project, if in the project the metadata.xml is located in the root module.

Affected version: 0.3.0

Remove unused properties and gui module

Implement centralized statistics gathering for cluster environment

See https://github.com/cuba-platform/cuba-jm/tree/centralized-monitoring and https://github.com/javamelody/javamelody/wiki/UserGuideAdvanced#7-automatic-registration-of-applications

Also, prepare a tutorial for setting up this monitoring for the clustered environment. Make sure that it works in docker-compose with load-balancer.

Description

Create information about Software Components file
https://doc.cuba-platform.com/manual-7.2/credits.html

Release 0.5.0 for cuba 7.0.0

Update javamelody-core to the latest version

JavaMelody statistics is cleared after tomcat restart

How to reproduce:

Deploy application with JavaMelody to a linux tomcat service. E.g. Ubuntu 18.04, "tomcat8" package.
Run for a while
Restart tomcat
Open /core-jm/ page again.

You will see that all graphs have been reset:

The reason is because JavaMelody by default stores its data in a temp directory. E.g. tomcat/temp/javamelody in tomcat-fast-deployment.
And linux tomcat service cleans temp directory on every server restart - which is reasonable thing. So javamelody stats are cleared during every tomcat service restart.

Suggestion: place javamelody stats to other place, e.g. work directory.

Easy default user and password is not secure

Having admin/admin by default is not secure. These values are easy to guess.

If deploying person forgets to change password (or he/she is not informed about this add-on attached to the system at all) - then we have an open administrative access window to the system to any who knows system URL and has access to web client.

Update installation instructions

Update the "Installation and configuration" section of readme.md: describe how to install the component using Add-ons Marketplace