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

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

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

The field 'name + command line' field is too long.
Do you want to truncate to 1000 bytes?

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 -Dcom.sun.management.jmxremote -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.osgi.framework.os.name=win32 -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

Environment

Processes probe 4.70

Resolution

Currently, the probe only supports 1000 bytes/chars in length for a command line to monitor a process. This is mentioned in the probe documentation:

https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/ca-unified-infrastructure-management-probes/GA/monitoring/systems-and-service-response/processes-process-monitoring/processes-process-monitoring-release-notes.html

 

 

 

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:

https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/ca-unified-infrastructure-management-probes/GA/monitoring/systems-and-service-response/processes-process-monitoring/processes-advanced-configuration.html#concept.dita_6d70db067a9ca2464c80dc5ea0263417c54ea342_UseRegularExpressions