Application Real-Time Monitoring Service:Integrate SkyWalking with ARMS

Step 1: Create a SkyWalking integration

1. Log on to the ARMS console. In the left-side navigation pane, choose Alert Management > Integrations.
2. On the Alert Integration tab, click Skywalking.
3. In the Create Skywalking Integration dialog box, enter a name and a description for the SkyWalking integration, specify the automatic recovery time of alert events, and then click Save.
   Note If an alert event is not triggered again within the specified period of time, the alert event is automatically cleared.
4. On the Alert Integration tab, find the SkyWalking integration that you created and copy the URL in the Integration Address column.
   

Step 2: Configure SkyWalking

1. Log on to the server where SkyWalking is deployed and go to the directory where the scripts of SkyWalking are located:

   cd /opt/sky/apache-skywalking-apm-bin/

2. Run the following command to view the config folder in the directory:

   ls config/

3. Run the following command to modify the alarm-settings.yml file in the config folder:

   vim config/alarm-settings.yml

4. Add the URL that you obtained in Step 1 to the webhook field:

   webhook
   - https://alerts.aliyuncs.com/api/v1/skywalking/event/******

5. Run the :wq command to save the changes to the alarm-settings.yml file.

(Optional) Step 3: Modify the integration

Alert Management provides field mappings between SkyWalking alert sources and ARMS alert events. You can also add or modify the mappings between fields on the Edit Integration page.

Sample alert source:

{
    "startTime":1630408697583,
    "scope":"SERVICE_INSTANCE",
    "scopeId":2,
    "name":"932******@127.0.XX.XX of testApp",
    "alarmMessage":"instance_jvm_cpu of 932******@127.0.XX.XX of testApp is more than 80 in 2 minutes of last 3 minutes",
    "ruleName":"instance_jvm_cpu_rule",
    "id1":"",
    "id0":"YnNtLXdlYg==.1_OTMyYjU1NmVmM2Y1NGR====--7p862kYTliODA4MTk0ZTJlODcxMWFAMTAuMS4xMS4xNg=="
}

1. On the Alert Integration tab, find the integration that you want to manage and click Edit in the Actions column.
2. In the Event Mapping section, click Send Test Data.
3. In the Send Test Data dialog box, enter the alert content of a third-party alert source in the JSON format and click Send.
   Note

   • If the message Uploaded. No events are generated. Configure mappings based on the original data. appears, the fields of the alert source are not mapped to the fields of ARMS alert events. The data that is sent is displayed in the left-side box. This allows you to select the source fields when you configure mappings.
   • If the message Uploaded. appears, the alert content is reported to the Alert Event History page. For more information, see View historical alert events.
4. In the Send Test Data dialog box, click Disable.
5. In the left part of the Event Mapping section, click the data records for which you want to configure mappings to view the details.
6. In the right part of the Event Mapping section, configure field mappings between the alert source and ARMS.
   1. Optional:In the Select Root Node section, specify whether to enable batch processing.
      If an array node exists in the alert data, you can specify the array node as the root node. The data that belongs to the root node is processed in a batch.

      After you select Use Batch Processing, select the array node to be processed as the root node.

      Note If multiple array nodes exist in the alert data, you can select only one of the array nodes for batch processing.
   2. In the Map Source Fields to Target Fields section, map the fields of the alert source to the fields of ARMS alerts.
      Click the Map icon to change the field mapping method.

      • Direct: The specified field of the alert source is mapped to the specified alert field of ARMS.
      • Series: You can use delimiters to concatenate multiple fields of the alert source into one field, and then map this field to the specified alert field of ARMS. Only special characters can be used as delimiters.
      • Condition: The specified fields of the alert source are mapped to the alert fields of ARMS only if the field values meet the specified conditions.
      • Mapping table: You must configure a mapping table that maps the severity levels of the alert source to the severity levels of ARMS alerts. You need to configure a mapping table only for the severity field.

      The following table describes the alert fields of ARMS.

      Alert field	Description
      alertname	The name of the custom alert.
      severity	The alert level. You must configure mappings for this field. The mapping method must be set to Direct.
      message	The description of the alert. The description is used as the content of the alert message. The description cannot exceed 15,000 characters in length.
      value	The sample value of a metric.
      imageUrl	The URL of the line chart that contains Grafana metrics. The URL is used to map the line chart.
      check	The check item of the alert. Examples: CPU, JVM, Application Crash, and Deployment.
      source	The source of the alert.
      class	The type of the object that triggers the alert event, for example, host.
      service	The source service of the alert. Example: Login Service.
      startat	The timestamp that represents the start time of the event.
      endat	The timestamp that represents the end time of the event.
      generatorUrl	The URL of the event details.

7. Configure field deduplication for alert events.
   To reduce duplicate data, the system uses relevant fields as the basis for deduplication. ARMS Alert Management allows you to preview the deduplication grouping results of historical event data that is displayed in the Event Mapping section. You can change the fields to be deduplicated.

   Note You can configure deduplication only for events that are not cleared.
   1. In the Event Deduplication section on the Integration Details page, select the fields that are used for deduplication.
      If multiple events have the same value for a specified field, the events are merged into one alert notification.
   2. Click Deduplication Test to preview the alert group after deduplication.
      Note The deduplication test takes effect only on the latest 10 data records that are uploaded in the left part of the Event Mapping section.
8. After you configure the settings, click Save.

View the details about an alert event

1. In the left-side navigation pane of the ARMS console, choose Alert Management > Alert Event History.
2. On the Alert Event History page, click the name of the alert event to view the event details. For more information, see View historical alert events.

Manage the integration

In the left-side navigation pane, choose Alert Management > Integrations. On the Alert Integration tab, you can perform the following operations on the integrations that you created:

• View the details of an integration: Find the integration and then click the row. On the Integration Details page, view the integration details.
• Update a key: Find the integration and then choose More > Update Key in the Actions column. In the message that appears, click OK.
  Important After you update the key, modify the alarm-settings.yml file based on the information in Step 2.
• Modify an integration: Find the integration and then click Edit in the Actions column. On the Integration Details page, modify the integration information and then click Save.
• Enable or disable an integration: Find the integration and then click Disable or Enable in the Actions column.
• Delete an integration: Find the integration and then click Delete in the Actions column. In the message that appears, click OK.
• Add an event processing flow to an integration: Find the integration and click Add Event Processing Flow in the Actions column. For more information, see Work with event processing flows.
• Create a notification policy: Find the integration for which you want to create a notification policy, and click More in the Actions column. In the list that appears, click Create Notification Policy. For more information, see Create and manage a notification policy.