Sumologic

JVM

JVM exposes metrics via JMX and we collect them using a lightweight JMX connector - Jolokia, that you need to run alongside your JVM instance (instructions below).

Our agent needs the Jolokia port and the username & password (if auth is enabled). If unspecified the default valued as below will be used.

The data.json entry for this plugin:

"jvm": {
     "port" : 8778,
     "username": "",
     "password": ""
 }

Having updated data.json on your server (no need to restart archagent), enable this plugin from the server's rule config page. Set thresholds for metrics that you care about and want to be alerted on. Enabling a plugin.

Setting up Jolokia

Download the stable release version of jolokia

# Find out the release version number of jolokia
jolokia_version=$(curl -s https://repo1.maven.org/maven2/org/jolokia/jolokia-jvm/maven-metadata.xml | grep "<release>" \
| sed "s/.*<release>\([^<]*\)<\/release>.*/\1/")

# Release version number of jolokia
echo "${jolokia_version}"

# Download the jolokia agent
curl "https://repo1.maven.org/maven2/org/jolokia/jolokia-jvm/${jolokia_version}/jolokia-jvm-${jolokia_version}-agent.jar" \
-o "jolokia-jvm-${jolokia_version}-agent.jar"

# Your jolokia agent name
echo "jolokia-jvm-${jolokia_version}-agent.jar"

Now connect jolokia to your JVM using the following command (to be run as the same user as the jvm process)

java -jar "jolokia-jvm-${jolokia_version}-agent.jar" start <pid_of_your_jvm>

If you see a Started Jolokia for PID ... message, we are done.

results matching ""

    No results matching ""