Processes probe - How to monitor a process with a command line with more than 1000 bytes/chars in length?


Article ID: 209157


Updated On:


DX Infrastructure Management


You want to monitor a java process running in a windows machine, and is getting the following message when creating the process monitoring profile:

Looking to the probe .cfg file, we can see the The "proc_cmd_line" parameter content of the related process monitoring profile is really being truncated after 1000 characters:

proc_cmd_line = C:\Program Files\Java\jre1.8.0_111\bin\java.exe -Xms8589934592 -Xmx8589934592 -cp "E:\Program Files\XXX XXXXXXXX\XXXXXXXX.\lib\com.XXX.arsys.boot-9.1.03-SNAPSHOT.jar" "-XX:OnOutOfMemoryError=taskkill /PID %p /F" -Dcom.XXX.arsys.boot.flavor=server -XX:+DisableExplicitGC -XX:NewRatio=2 -XX:MaxMetaspaceSize=512M -XX:MetaspaceSize=384M -Xss2M -Dlogback.configurationFile=file:./conf/logback_server.xml -Djavax.xml.transform.TransformerFactory=org.apache.xalan.processor.TransformerFactoryImpl -javaagent:./lib/spring-instrument-4.1.9.RELEASE.jar -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:+UseCompressedOops -Djava.library.path=./lib/upgradeutils/sqlauth/x64 -XX:HeapDumpPath=./Logs -XX:+HeapDumpOnOutOfMemoryError -XX:ErrorFile=file:./XXXXXXXX/db/XXXXXXXXjvmcrash_PID%p.log -Dorg.eclipse.equinox.http.jetty.autostart=false -Djetty.home=./jetty com.XXX.arsys.boot.Main --unicode -i "E:\Program Files\XXX XXXXXXXX\XXXXXXXX" -l "C:\Pro


Processes probe 4.70



There is an enhancement request already placed for this probe, to remove this limit. It will be implemented in the future, however, there is no ETA for this.

The workaround for this is to create a regex expression to match the process. This is described in the probe documentation: