All Products
Search
Document Center

Elastic Desktop Service:Use the monitoring and alerting features

Last Updated:Apr 02, 2026

Elastic Desktop Service (EDS) Enterprise tracks cloud computer usage, session connections, and bandwidth consumption. When a metric exceeds its configured threshold, the alerting system notifies your team so you can resolve issues before they affect end users.

This topic covers the full setup flow: creating alert contacts and contact groups, defining alert rules, configuring notification policies, and viewing alert records.

How it works

Before alerts can be delivered, set up three components in the following order:

  1. Alert contacts — the individuals who receive alert notifications. Each contact must verify their notification method (email or DingTalk chatbot) before they can receive alerts.

  2. Alert contact groups — collections of alert contacts. Alert rules are bound to contact groups, not to individual contacts.

  3. Alert rules — the conditions that trigger alerts, including which metric to monitor, the threshold, severity, and effective time window.

When an alert rule fires, the system sends a notification to the bound contact group. If the condition persists after the mute period ends, the system sends another notification.

Prerequisites

Before you begin, make sure you have:

  • Access to the EDS Enterprise console

  • At least one email address or DingTalk chatbot callback URL for alert contacts

Create alert contacts

An alert contact is a person designated to receive alert notifications.

  1. Log on to the EDS Enterprise console.

  2. In the left-side navigation pane, choose Monitoring & Alerts > Notifications & Alerts.

  3. Click the Contact Groups & Members tab, then click the Name tab.

  4. Click Create Contact. In the Create Contact panel, configure the following parameters and click Confirm.

    For DingTalk chatbot, enter the callback URL and click Test to complete verification. The chatbot takes effect only after successful verification.
    Parameter Description
    Name A name for the contact.
    Notification method At least one method is required: email address or DingTalk chatbot.
    Notification language Simplified Chinese, English, or follow the system language of the receiving device.

After creating a contact, the system sends an activation notification using the configured notification method. The contact must activate their notification method within 24 hours. Alerts are sent only to activated methods.

If the activation code expires, find the contact on the Name tab and click Resend Activation Code.

More operations

Operation Steps
Edit a contact On the Name tab, click Edit in the Actions column.
Delete a contact On the Name tab, click Delete in the Actions column. To delete multiple contacts at once, select them and use batch delete.

Create an alert contact group

An alert contact group is a set of alert contacts. Alert rules are bound to contact groups rather than individual contacts.

Make sure at least one alert contact exists before creating a group.

  1. In the left-side navigation pane, choose Monitoring & Alerts > Notifications & Alerts.

  2. Click the Contact Groups & Members tab, then click the Contact Groups tab.

  3. Click Create Contact Group. In the Create Contact Group panel, configure the following parameters and click Confirm.

    Only activated contacts can receive alert notifications. Make sure all contacts in the group have activated their notification methods.
    Parameter Description
    Group name A name for the contact group.
    Remarks (Optional) A description or comments for the group.
    Add contacts Select at least one contact.

More operations

Operation Steps
Add or remove contacts On the Contact Groups tab, click View/Add Contacts in the Actions column for the group.
Delete a contact group On the Contact Groups tab, click Delete in the Actions column. Deleting a group removes contacts from the group but does not delete the contacts themselves.

Create an alert rule

An alert rule defines the conditions that trigger an alert, including the monitored resource, metric, threshold, severity level, and the time window during which the rule is active.

Make sure at least one alert contact group exists before creating an alert rule.

Steps

  1. In the left-side navigation pane, choose Monitoring & Alerts > Notifications & Alerts.

  2. Click the Alert Rules & Records tab, then click the Alert Rules tab.

  3. Click Create Alert Rule. In the Create Alert Rule panel, configure the following parameters and click OK.

Common parameters

Parameter Description Example
Rule name A name for the alert rule. CPU usage alert
Alert source The type of resource to monitor: Cloud Computer or Premium Bandwidth. Cloud Computer
Monitoring scope All Resources: applies to all cloud computers or all premium bandwidth instances. Cloud Computer or Premium Bandwidth: applies to the selected resources only. All Resources
Metric type Single Metric: monitors one metric, with alert rules at different severity levels. Multiple Metrics: monitors multiple metrics simultaneously at the same severity level. Single Metric
Effective period The time window during which the rule is active. Outside this window, the rule does not trigger. 08:00–09:59
Mute period The minimum interval between consecutive notifications from the same alert rule. If the condition is still met after the mute period ends, the system sends another notification. 30 minutes
Alert contact group The contact group that receives alert notifications. O&M Group

Parameters for Single Metric

Parameter Description Example
Metric The metric to monitor. CPU Used by Current User Space (%)
Severity & rule The threshold condition at each severity level. At least one condition is required. Severity levels and their notification channels: Critical (phone + SMS + email + DingTalk), Warning (SMS + email + DingTalk), Info (email + DingTalk). Warning: average value in 3 consecutive periods > 80%

Parameters for Multiple Metrics

Parameter Description Example
Severity The severity level for all conditions in this rule: Critical, Warning, or Info. Warning
Multi-metric alert condition The threshold condition for each metric. Up to 10 conditions. Average disk usage > 80%; average memory usage > 60%
Metric relationship Trigger alert when all conditions are met: alerts when every condition is true (logical AND). Trigger alert when any condition is met: alerts when at least one condition is true (logical OR). Trigger alert when any condition is met
Trigger condition The number of consecutive evaluation periods all conditions must be met before an alert fires. 3 consecutive periods

More operations

Operation Steps
Modify a rule On the Alert Rules tab, click Modify in the Actions column.
Disable a rule On the Alert Rules tab, click Disable in the Actions column, then click Confirm. When disabled, the system continues monitoring the metric but does not send notifications even if the threshold is exceeded.
Enable a rule On the Alert Rules tab, click Enable in the Actions column, then click Confirm.
Delete a rule On the Alert Rules tab, click Delete in the Actions column, then click Confirm.

Configure notification policies

Notification policies are predefined by WUYING Workspace. Enable a policy and configure its notification rules to start receiving notifications when the policy conditions are met.

Configure a notification rule

  1. In the left-side navigation pane, choose Monitoring & Alerts > Notifications & Alerts.

  2. Click the Notification Policies & Records tab, then click the Notification Policy tab.

  3. In the Actions column for the target notification policy, click Configure Notification Rule. Configure the parameters and click Confirm.

The following policies are available:

User status changed to resigned

Supported account types: convenience accounts, DingTalk, WeChat Work, and Lark.

When a user account is offboarded, the system sends a notification to the configured contact group. After receiving the notification, you can decide whether to delete the account, transfer assets, or reassign the associated cloud computer resources.

Parameter Description Example
Notification period The day(s) on which to send notifications. At least one day required. Friday
Notification time The time to send the notification. At least one time point required, up to two. All times are in UTC+8. 17:00
Notification rule Describes the current policy rule. No configuration required.
Contact group The contact group that receives notifications. O&M Group

Prolonged user inactivity

Supported account types: convenience accounts, DingTalk, WeChat Work, Lark, and Active Directory (AD) accounts.

When a user has not connected to their cloud computer for a specified number of days, the system sends a notification. Use this to identify unused resources and decide whether to reclaim or reassign them.

Parameter Description Example
Notification schedule The day(s) on which to send notifications. At least one day required. Friday
Notified at The time to send the notification. At least one time required, up to two. All times are in UTC+8. 17:00
Custom duration The number of days of inactivity that triggers a notification. At least one threshold required, up to three. 30 days
Contact group The contact group that receives notifications. Ops Team 1

More operations

Operation Steps
Enable or disable a policy On the Notification Policies tab, click Enable or Disable in the Actions column. When the "User account status changed to resigned" policy is enabled, the system sends a notification whenever a user account (including WUYING convenience accounts) changes to resigned status. You can then decide whether to delete the account, transfer assets, or reassign cloud computer resources. For more information, see Manage resigned convenience accounts.
View notification records Click the Notification Policies & Records tab, then click Notification Records. Click View Details in the Actions column for the target policy.

View alert records

  1. In the left-side navigation pane, choose Monitoring & Alerts > Notifications & Alerts.

  2. Click the Alert Rules & Records tab, then click the Alert Rules tab.

  3. View alert records using either of the following methods:

    • Click the Alert History tab. Enter an alert rule name or ID to filter records. To export records, click the Export icon in the upper-right corner.

    • On the Alert Rules tab, click View Details in the Actions column for a specific rule. On the Alert Records page, select a preset time period or specify a custom range.

Troubleshooting

Alert rule is configured but no alerts are received

Cause: CloudMonitor agent collects metric data from cloud computers. By default, the agent is disabled — if it is not running, no metric data is collected and no alerts are triggered.

Resolution: Enable CloudMonitor agent on the affected cloud computer.

  1. On your cloud computer, press Win+R, enter services.msc in the Run window, and press Enter.

  2. In the Services window, find argusagent service, right-click it, and select Properties.

  3. On the General tab, set Startup type to Automatic. If the service is not running, click Start under Service status, then click OK.

After starting the agent, metric data begins flowing to the monitoring system and alert rules can trigger normally.