I've tried to reproduce with the same stack version and Java agent version and it seems that metrics are properly captured, however, the rounding in the UI could definitely cause some confusion here as overlay is shown with the biggest unit (here GB).
you likely have set a limit to 1.3gb with -Xmx, thus the overlay uses gigabyte as units.
the application currently have a very small usage of heap (less than 100mb), thus it gets rounded to 0.0 GB in the overlay.
Could you try to let the application run for a while with some activity so we can see how does the metrics look like when the heap usage goes over 100mb ?
Alternatively, could you try to remove the -Xmx argument from your JVM ? with that the heap usage should be shown in megabytes instead of gigabytes, hence there shouldn't be any rounding here.
I deploy it in a container, and in order to prevent memory overflow, XMX is calculated. In the production environment, I am currently afraid to delete XMX
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.