Metricly’s Java agent is a java monitoring agent with a programmable bytecode instrumentation engine that’s enabled by adding a JVM integration in Metricly. The Metricly Java integration allows Metricly to collect JVM runtime system metrics like CPU, Memory, GC, Threads and Classes Count, and application components method performance statistics, such as number of calls and execution time.
Must have Java 6 Or greater.
netuitive-zorka.zipfile to the desired location. We recommend that you unzip the
netuitive-zorka.zipfile near the app it is monitoring.
You can also use the following command to obtain the most recent version of the Java Agent:
curl -s https://api.github.com/repos/Netuitive/zorka/releases/latest | jq -r ".assets | .browser_download_url"
zorka.propertiesfile that was included in the
jvm.bshscript and any other scripts as necessary at the top of the file.
zorka.propertiesfile and include the name of each element. The default setting (
cluster 2) would create a JVM () element and two CLUSTER () elements with the names
zorka.clusters = cluster1, cluster2
zorka.clusters.type = CLUSTER
netuitive.api.keyvalue to the unique API key generated for your account that you copied in step 1.
This integration’s package (computed metrics, dashboards, and policies that will give you important events and alerts) will be automatically enabled and provisioned to your account as soon as Metricly receives data from the integration. The PACKAGES button on the integration setup page will become active once data is received, so you’ll be able to disable and re-enable the package at will.
We want to run the java application
zorka-core-test.jar with our Java agent specified in the
-javaagent JVM option.
java -javaagent:/opt/netuitive-zorka/netuitive.jar=/opt/netuitive-zorka -jar zorka-core-test.jar