Cloud Monitor:Event subscription

Scenario: monitor the status of the Cloud Monitor agent

To monitor the running status of the Cloud Monitor agent, use an event subscription to subscribe to agent status events, so that an anomaly alert is generated when the agent becomes abnormal. When you create a subscription policy, select cloud service monitoring event subscription, set the service to Cloud Monitor, and then select the Cloud Monitor agent started (running normally) or Cloud Monitor agent running abnormally event from the Event Name drop-down list. When the agent status changes and matches the subscription conditions, the system sends alert information to the notification recipients based on the notification policy that you selected.

Currently, you cannot directly monitor data reporting failures or the agent heartbeat. Use the preceding agent status events to indirectly determine whether the agent is abnormal.

Create a subscription policy

1. Log on to the Cloud Monitor 2.0 console, select the target workspace, and in the left-side navigation pane, choose All Features > Event Center.

2. In the navigation pane of Event Center, choose Event Management > Event Subscription.

3. On the Event Subscription page, click Create a subscription policy.

4. In the Create a subscription policy dialog box, configure the following parameters.

   Parameter	Description
   Name	The name of the subscription policy.
   Description	A description of the subscription policy.
   Alert Subscription	Select how the policy matches events: The event must meet Any/All/Composite the following conditions. Unlimited: Subscribes to all events without filtering. Condition 1: Click Add Condition to set multiple conditions. Event source type Severity level Alert status Alert name
   Advanced subscription settings	Select the workspaces to subscribe to. You can subscribe to events from multiple workspaces.
   Notification Policies	The notification method, recipients, and template to use when an event triggers the policy. Select a preset notification policy. Select a custom notification policy. Create a new notification policy while creating the subscription policy.
   Integration Policy	Runs the selected integration automatically when an alert is triggered or resolved.

5. After you complete the settings, click OK.

Manage subscription policies

1. The Event Subscription page lists all subscription policies you have created. The list includes the following fields:

   Field	Description
   Name	The name of the subscription policy.
   Description	The description of the subscription policy.
   Subscription scope	The number of filter conditions. Hover over the value to view details.
   Notification policy	The name of the associated notification policy.
   Migration source	The source of the subscription policy.
   Status	Whether the policy is enabled or disabled.
   Actions	Available operations, such as Edit and Delete.

2. Supported filters:

   • Status filter: Filter subscription policies by their enabled or disabled status.

   • Search by name: Search for a subscription policy by name. Fuzzy matching is supported.

3. To enable or disable a subscription policy, click the toggle in the Status column for the policy.

   Note

   • After a policy is disabled, it no longer matches or processes new events.

   • Existing alerts are not affected and continue to be processed based on their original logic.

4. Edit an event subscription:

   1. To modify a subscription policy, click Edit in the Actions column.

      Note

      • Subscription policies migrated from ARMS (with a notifyStrategyId that starts with arms_) cannot be edited.

      • Subscription policies migrated from CMS (with a notifyStrategyId that starts with cms_) are view-only.

5. Delete an event subscription:

   1. To delete a subscription policy, click Delete in the Actions column.

      Note

      • Subscription policies migrated from ARMS or CMS cannot be deleted.

      • After a policy is deleted, the processing of alerts associated with it stops immediately.

When an event subscription uses a Webhook integration to push alerts to ARMS, that Webhook replaces the custom Webhook notification recipient already configured in the notification policy. After the configuration takes effect, the alert group receives only the alerts pushed by ARMS, and the Webhook alerts originally configured in Cloud Monitor are no longer pushed to that group. To receive both kinds of alerts, configure the ARMS notification and the Cloud Monitor Webhook notification to send to different chat groups.