ARMS Alert Management allows you to route events about status changes in the alert lifecycle, such as alert creation, claim, and close, to your EventBridge event bus. By consuming these events, you can integrate with third-party systems for automated remediation or ticketing system integration. This topic describes how to route alert events from ARMS Alert Management to an EventBridge event bus.
Background information
EventBridge is a serverless event bus service provided by Alibaba Cloud that allows you to connect Alibaba Cloud services, custom applications, and SaaS applications in a standardized and centralized way. You can use EventBridge to route events between these applications based on the CloudEvents 1.0 protocol, which helps you build loosely coupled, distributed, event-driven architectures. For more information, see What is EventBridge?
Step 1: Create EventBridge resources
Create an EventBridge event bus. For more information, see Manage custom event buses.
After you create the event bus, obtain the public endpoint from the Event Bus Overview page.
Add an event source of the custom application type. For more information, see Manage custom event sources.
In the dialog box, set a Name (for example,
arms) and an optional Description.
Step 2: Configure the EventBridge integration in ARMS
-
Log on to the ARMS console. In the left-side navigation pane, choose .
On the Integrations page, click the Notification Integration tab, and then click EventBridge.
In the Add Integration dialog box, configure the following parameters and click Save.
Parameter
Description
Name
A custom name for the integration, for example,
EventBridge-integration.Description
An optional description for the integration.
Endpoint
The public endpoint that you obtained in Step 1.
AccessKey
The AccessKey ID of your Alibaba Cloud account. For more information, see Obtain an AccessKey pair.
AccessKey Secret
The AccessKey secret of your Alibaba Cloud account. For more information, see Obtain an AccessKey pair.
Message Bus Name
The name of the event bus that you created in Step 1. For example,
armstest.regionId
The ID of the region where the event bus that you created in Step 1 is located. For example,
cn-hangzhou.Event Source Name
The name of the event source that you created in Step 1. For example,
arms.
Step 3: Configure a notification policy
In a notification policy, set Ticket System to the EventBridge integration that you created in the previous step. For more information, see Notification policies.
Step 4: View alert events in the EventBridge console
Log on to the EventBridge console to view alert events. For more information, see Query events. On the Event Trace page of your target event bus, select the Query by time range tab to view the alert events sent from ARMS. The event types include aliyun:arms:alarm:create (Alert creation event), aliyun:arms:alarm:claim (Alert claim event), aliyun:arms:alarm:comment (Alert comment event), and aliyun:arms:alarm:close (Alert close event). You can click Event Trace or Event Detail for detailed information.
Event Type Code | Type |
aliyun:arms:alarm:create | Alert creation event |
aliyun:arms:alarm:claim | Alert claim event |
aliyun:arms:alarm:comment | Alert comment event |
aliyun:arms:alarm:close | Alert close event |
In the Actions column for an event, click Event Details to view its parameters. The following sections show the payload format for each event type.