Server monitoring

Applies to 1.0.0. Tasks → New/Edit → plugin SERVER_MONITOR.

Before you start

Use ADMIN to create, configure and save tasks. ADMIN or OPERATOR can execute published definitions; ADMIN reads detailed logs and input/output variables. Resources must be enabled and reachable from the execution node. See tasks for common timeout, retry and version settings, and the permission matrix.

Field reference

“Default” means the initial value of a new 1.0.0 form. An empty value means the field has not been filled in; required fields still need a value. Visibility follows the selected branch; conditional requirements apply only to that branch.

Collection

• Monitor server: Provide the monitoring-agent connection for the monitored server.
• Collection items: CPU/MEMORY/DISK/NETWORK/APPLICATION, without duplicates.

Application collection

• Application name: Unique application name in the monitor configuration; at most 64 applications and 128 characters per name.
• Match type: Choose PROCESS_NAME, COMMAND, PID or REGEX to match processes.
• Match value: Provide the value required by the selected match type; PID must be a positive integer and regex patterns are limited to 256 characters.
• Must be running: Specify whether the application must be running.
• Allow multiple processes: Specify whether multiple processes may match the application.

System thresholds

• Warning: Network rates use B/s; CPU, memory and disk use percentages.
• Critical: The critical threshold cannot be lower than the warning threshold.
• Warning: Network rates use B/s; CPU, memory and disk use percentages.
• Critical: The critical threshold cannot be lower than the warning threshold.
• Warning: Network rates use B/s; CPU, memory and disk use percentages.
• Critical: The critical threshold cannot be lower than the warning threshold.
• Warning: Network rates use B/s; CPU, memory and disk use percentages.
• Critical: The critical threshold cannot be lower than the warning threshold.
• Warning: Network rates use B/s; CPU, memory and disk use percentages.
• Critical: The critical threshold cannot be lower than the warning threshold.

Each enabled rule requires a warning or critical threshold; critical cannot be below warning. CPU, memory and disk use percentages; network rates use B/s.

Disk

• Disk path overrides: Match the full path; use default thresholds when no override matches.

Application thresholds

• CPU (%): Application names must match collection settings; CPU is a percentage and memory is in MiB.
• Memory (MiB): Application names must match collection settings; CPU is a percentage and memory is in MiB.

Alerts

• Send monitor alerts: Send monitoring alerts from rule results when enabled.
• Notification configuration: Select the notification configuration for monitoring alerts.

Behavior and boundaries

• Enable at least one valid rule; rules can be configured only for collected metrics.
• Recovery notifications and cross-run alert deduplication are unsupported; notify.recovery=true is rejected.
• The first rate sample may be 0; missing metrics differ from actual zero values.

Typical configuration: Collect CPU and memory metrics

Fill in the form below, replacing resource names with your enabled resources. This is a configuration guide, not importable JSON. Follow the tutorial linked below for data preparation and execution.

Prepare an authenticated monitoring agent reachable from the Worker. Threshold results depend on actual metrics; this example does not guarantee a healthy result.

Expected result: Timestamps and metrics are current and valid; threshold results are interpretable. An alert does not automatically mean task execution failed.

Follow the full tutorial. Save the definition before running it; inspect execution state and business results separately.

Configuration keys

Use these keys when inspecting imported configuration, API payloads or errors. [] denotes a collection item; the form does not require you to enter key names.

Related pages

Tasks and versions · Parameters and expressions · Scenario tutorials