Settings 2.0 - Built-in process monitoring rules schema
Built-in process monitoring rules (builtin:process.built-in-process-monitoring-rule)
Enable or disable built-in monitoring rules.
| Schema ID | Schema groups | Scope |
|---|---|---|
builtin:process.built-in-process-monitoring-rule |
| HOST_GROUP - Host Groupenvironment |
Parameters
| Property | Label | Type | Description | Required |
|---|---|---|---|---|
| -2 | Do not monitor processes if EXE name equals 'php-cgi' | boolean | Rule id: 2 | required |
| -3 | Do monitor processes if ASP.NET Core application path exists | boolean | Rule id: 3 | required |
| -4 | Do monitor processes if EXE name equals 'w3wp.exe' | boolean | Rule id: 4 | required |
| -49 | Do not monitor processes if EXE name equals 'filebeat' | boolean | Rule id: 49 | required |
| -50 | Do not monitor processes if EXE name equals 'metricbeat' | boolean | Rule id: 50 | required |
| -51 | Do not monitor processes if EXE name equals 'packetbeat' | boolean | Rule id: 51 | required |
| -52 | Do not monitor processes if EXE name equals 'auditbeat' | boolean | Rule id: 52 | required |
| -53 | Do not monitor processes if EXE name equals 'heartbeat' | boolean | Rule id: 53 | required |
| -54 | Do not monitor processes if EXE name equals 'functionbeat' | boolean | Rule id: 54 | required |
| -47 | Do not monitor processes if Go Binary Linkage equals 'static' | boolean | Rule id: 47 | required |
| -5 | Do monitor processes if EXE name equals 'caddy' | boolean | Rule id: 5 | required |
| -6 | Do monitor processes if EXE name equals 'influxd' | boolean | Rule id: 6 | required |
| -7 | Do monitor processes if EXE name equals 'adapter' | boolean | Rule id: 7 | required |
| -8 | Do monitor processes if EXE name equals 'auctioneer' | boolean | Rule id: 8 | required |
| -9 | Do monitor processes if EXE name equals 'bbs' | boolean | Rule id: 9 | required |
| -10 | Do monitor processes if EXE name equals 'cc-uploader' | boolean | Rule id: 10 | required |
| -11 | Do monitor processes if EXE name equals 'doppler' | boolean | Rule id: 11 | required |
| -12 | Do monitor processes if EXE name equals 'gorouter' | boolean | Rule id: 12 | required |
| -13 | Do monitor processes if EXE name equals 'locket' | boolean | Rule id: 13 | required |
| -14 | Do monitor processes if EXE name equals 'metron' | boolean | Rule id: 14 | required |
| -16 | Do monitor processes if EXE name equals 'rep' | boolean | Rule id: 16 | required |
| -17 | Do monitor processes if EXE name equals 'route-emitter' | boolean | Rule id: 17 | required |
| -18 | Do monitor processes if EXE name equals 'route-registrar' | boolean | Rule id: 18 | required |
| -19 | Do monitor processes if EXE name equals 'routing-api' | boolean | Rule id: 19 | required |
| -20 | Do monitor processes if EXE name equals 'scheduler' | boolean | Rule id: 20 | required |
| -21 | Do monitor processes if EXE name equals 'silk-daemon' | boolean | Rule id: 21 | required |
| -22 | Do monitor processes if EXE name equals 'switchboard' | boolean | Rule id: 22 | required |
| -23 | Do monitor processes if EXE name equals 'syslog_drain_binder' | boolean | Rule id: 23 | required |
| -24 | Do monitor processes if EXE name equals 'tps-watcher' | boolean | Rule id: 24 | required |
| -25 | Do monitor processes if EXE name equals 'trafficcontroller' | boolean | Rule id: 25 | required |
| -26 | Do not monitor processes if Node.js application base directory ends with '/node_modules/prebuild-install' | boolean | Rule id: 26 | required |
| -27 | Do not monitor processes if Node.js application base directory ends with '/node_modules/npm' | boolean | Rule id: 27 | required |
| -28 | Do not monitor processes if Node.js application base directory ends with '/node_modules/grunt' | boolean | Rule id: 28 | required |
| -29 | Do not monitor processes if Node.js application base directory ends with '/node_modules/typescript' | boolean | Rule id: 29 | required |
| -45 | Do not monitor processes if Node.js application equals 'yarn' | boolean | Rule id: 45 | required |
| -68 | Do not monitor processes if Node.js application equals 'corepack' | boolean | Rule id: 68 | required |
| -32 | Do not monitor processes if Node.js application base directory ends with '/node_modules/node-pre-gyp' | boolean | Rule id: 32 | required |
| -33 | Do not monitor processes if Node.js application base directory ends with '/node_modules/node-gyp' | boolean | Rule id: 33 | required |
| -34 | Do not monitor processes if Node.js application base directory ends with '/node_modules/gulp-cli' | boolean | Rule id: 34 | required |
| -35 | Do not monitor processes if Node.js script equals 'bin/pm2' | boolean | Rule id: 35 | required |
| -36 | Do not monitor processes if Cloud Foundry application begins with 'apps-manager-js' | boolean | Rule id: 36 | required |
| -55 | Do not monitor processes if EXE name equals 'grootfs' | boolean | Rule id: 55 | required |
| -56 | Do not monitor processes if EXE name equals 'tardis' | boolean | Rule id: 56 | required |
| -43 | Do not monitor processes if EXE path begins with '/tmp/buildpacks/' | boolean | Rule id: 43 | required |
| -37 | Do monitor processes if Cloud Foundry application exists | boolean | Rule id: 37 | required |
| -38 | Do not monitor processes if Kubernetes container name equals 'POD' | boolean | Rule id: 38 | required |
| -39 | Do not monitor processes if Docker stripped image contains 'pause-amd64' | boolean | Rule id: 39 | required |
| -44 | Do not monitor processes if EXE name equals 'oc' | boolean | Rule id: 44 | required |
| -58 | Do not monitor processes if EXE name equals 'calico-node' | boolean | Rule id: 58 | required |
| -67 | Do not monitor processes if EXE path equals '/usr/bin/piper' | boolean | Rule id: 67 | required |
| -69 | Do not monitor processes if Kubernetes container name equals 'cassandra-operator' | boolean | Rule id: 69 | required |
| -70 | Do not monitor processes if EXE name contains 'UiPath' | boolean | Rule id: 70 | required |
| -40 | Do monitor processes if Kubernetes namespace exists | boolean | Rule id: 40 | required |
| -41 | Do monitor processes if container name exists | boolean | Rule id: 41 | required |
| -46 | Do not monitor processes if EXE path equals '/opt/cni/bin/host-local' | boolean | Rule id: 46 | required |
| -48 | Do not monitor processes if EXE name begins with 'mqsi' | boolean | Rule id: 48 | required |
| -57 | Do not monitor processes if Java JAR file begins with 'org.eclipse.equinox.launcher' | boolean | Rule id: 57 | required |
| -59 | Do not monitor processes if EXE name equals 'casclient.exe' | boolean | Rule id: 59 | required |
| -60 | Do not monitor processes if JAR file name equals 'dynatrace_ibm_mq_connector.jar' | boolean | Rule id: 60 | required |
| -61 | Do not monitor processes if EXE name contains 'Agent.Worker' | boolean | Rule id: 61 | required |
| -62 | Do not monitor processes if ASP.NET Core application DLL contains 'Agent.Worker' | boolean | Rule id: 62 | required |
| -63 | Do not monitor processes if EXE name contains 'Agent.Listener' | boolean | Rule id: 63 | required |
| -64 | Do not monitor processes if ASP.NET Core application DLL contains 'Agent.Listener' | boolean | Rule id: 64 | required |
| -65 | Do not monitor processes if EXE name equals 'FlexNetJobExecutorService' | boolean | Rule id: 65 | required |
| -66 | Do not monitor processes if EXE name equals 'FlexNetMaintenanceRemotingService' | boolean | Rule id: 66 | required |