Skip to main content

Node Monitoring and Alerts

Use this page to review monitoring data and manage alert rules for an existing node in MyAccount.

The node details page exposes two node-specific surfaces: the node summary area on the details page (uptime, memory chart, storage chart, and the Test Monitoring Service action) and the node Alerts tab. Both depend on the node monitoring agent being reachable from the node.

For the full monitoring graph reference, agent setup, and account-level alert dashboards, see Node Monitoring.

note

Monitoring data and alert actions require an active monitoring connection for the node. After node creation, restart, or volume mount, wait a few minutes before checking graphs or creating alerts.

Open Node Monitoring and Alerts​

  1. Log in to MyAccount.
  2. Go to Compute > Nodes.
  3. Select the node.
  4. Use the node details page for Node Uptime, Test Monitoring Service, memory and storage charts, and the monitoring agent status banner.
  5. Open the Alerts tab on the node details page to create or manage alerts for that node.

The flows below assume you have already selected the node.

Node Details Monitoring Surface​

The node summary on the details page shows monitoring data inline when the agent is reachable. It can include:

  • Node Uptime
  • Memory usage chart sized to node RAM
  • Storage usage chart sized to node disk
  • A warning banner with a troubleshooting link when the monitoring agent is unavailable

When the monitoring agent cannot be reached, MyAccount hides the charts, shows the agent warning, and links to troubleshooting steps instead of node uptime and resource graphs.

Test Monitoring Service​

Use Test Monitoring Service to check whether MyAccount can reach the monitoring agent on the node.

  1. Open the node details page.
  2. Select Test Monitoring Service.
  3. Wait for the result indicator next to the button.
  4. If the test reports a failure, follow the troubleshooting link shown with the agent warning.

Test Monitoring Service is not available when the node is Powered off. Start the node before running the test.

Attached Volume Monitoring​

If the node has attached volumes, each volume has a Monitoring view on the node's attached volume area.

For Linux nodes, attached-volume monitoring is not active until the portal-provided command is added to the monitoring agent configuration inside the node. The Monitoring view shows the exact command and a copy icon when monitoring is not enabled. Windows nodes do not require the manual command.

To enable attached-volume monitoring on a Linux node:

  1. Open the attached volume Monitoring view.
  2. Copy the command shown in the portal.
  3. SSH into the node.
  4. Run the command with the required privileges.
  5. Wait 10 to 15 minutes after the volume is mounted or monitoring is enabled before checking the graphs.

Node Alerts Tab​

The node Alerts tab lists the alert rules attached to that node. The table shows:

  • Alert Type with the trigger icon
  • Alert Condition, written as a sentence describing the operator and threshold
  • Actions to pause, resume, or delete each alert

For alerts that already exist, the Actions column shows pause when the alert is running and resume when the alert is paused.

To view or edit alerts across all monitored resources, use the Monitoring Dashboard link in the Alerts tab. That link opens the global alert management page documented in Node Monitoring.

note

The Alerts tab disables alert actions for Disaster Recovery target nodes. Create Alert is also disabled while the node is not Running.

Create a Node Alert​

Use this flow when you are viewing a node and want to add an alert for that node.

  1. Open the node Alerts tab.
  2. Select Create Alert.
  3. In Alert trigger type, select one of:
    • Processor Load
    • Consumed Memory
    • Free Disk Space
    • Volume Read Ops
    • Volume Write Ops
    • Webcheck
  4. If you selected Free Disk Space, Volume Read Ops, or Volume Write Ops, select the Volume:
    • Node Volume(Default) for the boot or default node volume.
    • The attached volume name when the alert should track an attached volume.
  5. For non-Webcheck triggers, select an Operator:
    • Greater than
    • Less than
    • Equal to
    • Not equal to
  6. For non-Webcheck triggers, enter the Threshold value:
    • 10 to 100 for processor, memory, and disk percentage triggers.
    • 1 to 75000 for volume read or write operation triggers.
  7. For non-Webcheck triggers, select a Severity (Not classified, Information, Warning, Average, High, or Disaster).
  8. For Webcheck, enter:
    • Monitor URL (HTTP 200)
    • Webcheck Interval (15, 30, 45, or 60 seconds)
    • Contain Content/Text for the expected response text
  9. Select one or more Alert Group(s) that should receive notifications. Use All to select every available alert group.
  10. Review the Alert Summary.
  11. Select Create.

The new alert appears in the node Alerts tab. The same alert is also visible from the global alert management page.

If no alert group exists yet, create one inline from the add icon in Alert Group(s). Alert groups, severity behavior, and notification delivery are described in Node Monitoring.

Pause, Resume, or Delete a Node Alert​

Use the Actions column in the node Alerts tab.

Pause an Alert​

  1. Find the alert in the node Alerts tab.
  2. Select the Pause Alert icon.
  3. Confirm the pause action.

The alert stays configured but stops sending notifications until it is resumed.

Resume an Alert​

  1. Find the paused alert in the node Alerts tab.
  2. Select the Resume Alert icon.
  3. Confirm the resume action.

The alert resumes evaluation and notifications.

Delete an Alert​

  1. Find the alert in the node Alerts tab.
  2. Select the delete icon.
  3. In the confirmation dialog, select Delete.

The alert and its underlying trigger are removed for that node.

warning

Pause, resume, and delete are disabled in the node Alerts tab when the node is a Disaster Recovery target. Manage those alerts from the source node instead.

Webcheck Behavior​

Webcheck is available from the node Alerts tab only. It checks that a URL returns HTTP 200 and that the response contains the required text. If the response does not contain the required text, the alert condition is met.

The portal prevents creating a duplicate Webcheck with the same URL and required text for the same host. Existing node monitoring also limits the number of Webchecks per host.

For severity, operator, and threshold mechanics, Webcheck does not use them — the trigger is matched internally when the required text is missing.

ResourceUse it for
Manage NodesReturn to the node management overview.
Node ActionsLifecycle actions that affect node state and monitoring availability.
Action AvailabilityShared reasons node actions are hidden, disabled, or rejected.
Node MonitoringFull monitoring graph reference, alert groups, dashboards, and notification settings.
Monitoring AlertsAlert group setup and how monitoring alerts are delivered.
Zabbix AgentMonitoring agent installation, status checks, and firewall requirements.
Monitoring TroubleshootingDetailed troubleshooting for missing monitoring data.
Last updated on May 15, 2026.