Help Center/ Cloud Eye/ Best Practices/ Alarm Notification Methods/ Receiving Alarm Notifications via HTTP/HTTPS
Updated on 2026-11-20 GMT+08:00

Receiving Alarm Notifications via HTTP/HTTPS

In enterprise O&M environments, alarm notifications need to be sent to multiple third-party systems, such as service ticket platforms and in-house monitoring centers. Traditional email and SMS channels are limited in flexibility, allowing only manual message notification. They lack structured parsing, automated transfer, and custom processing capabilities. Alarm notifications can be received through HTTP/HTTPS channels. When an alarm is triggered, the notification is received in JSON format. The notification can be parsed and subsequent logic can be executed as needed, enabling seamless integration of alarms with HTTP-compliant systems and enhancing O&M automation and response efficiency.

When you configure an alarm contact, if you select HTTP or HTTPS as the notification channel and enter a public HTTP/HTTPS address, an alarm notification will be sent to that address when the resource metric reaches the alarm condition.

Procedure

For details about the process and description of receiving alarm notifications through HTTP or HTTPS, see Table 1.

Table 1 Process of receiving alarm notifications through HTTP or HTTPS

No.

Step

Description

1

Adding an HTTP/HTTPS Public Address for a Contact

Configure a public address for receiving alarm notifications. When an alarm is triggered, an HTTP/HTTPS request is sent to this address to push structured alarm data.

2

Creating an Alarm Contact Group and Adding Alarm Contacts

Define an alarm contact group and add HTTP/HTTPS contacts to the group so that the group can be referenced in alarm rules.

3

Creating a Notification Template

Create a notification template to ensure that the recipient can parse key fields as required and meet the requirements for structured alarm messages.

4

Creating an Alarm Rule

Set monitoring metrics and alarm policies for triggering alarms, and bind the alarm rules to the contact group and notification template.

5

Viewing Alarm Notifications

Verify that alarms are sent and received as expected.

Adding an HTTP/HTTPS Public Address for a Contact

  1. Log in to the Cloud Eye console.
  2. In the navigation pane, choose Alarm Management > Alarm Notifications.
  3. Click the Contacts tab.
  4. Click Create. The Create Contact page is displayed.
    Figure 1 Creating a contact
  5. Configure contact information as prompted, as shown in Table 2.
    Table 2 Parameters for creating a contact

    Parameter

    Example Value

    Description

    Contact Name

    notification-http

    Contact name. Enter 1 to 42 characters.

    Protocol

    • Select HTTP and enter the public network address in the text box of the selected protocol.

      Example: http://example.com/notification/action

    • Select HTTPS and enter the public network address in the text box of the selected protocol.

      Example: https://example.com/notification/action

      NOTE:

      The HTTP/HTTPS address you provide is an accessible public address.

    Over which protocol alarm notifications will be sent. Only one object can be added for each protocol.

  6. Click Create.

Creating an Alarm Contact Group and Adding Alarm Contacts

  1. Log in to the Cloud Eye console.
  1. In the navigation pane, choose Alarm Management > Alarm Notifications.
  2. Click the Contact Groups tab.
  3. Click Create. The Create Contact Group page is displayed.
    Figure 2 Creating a contact group
  4. Configure contact group information as prompted, as shown in Table 3.
    Table 3 Parameters for creating a contact group

    Parameter

    Example Value

    Description

    Group

    Contact_Group-http

    Contact group name. Enter 1 to 64 characters. Only letters, digits, underscores (_), and hyphens (-) are allowed.

    Enterprise Project

    default

    Enterprise project to which the contact group belongs. Only users with the enterprise project permissions can view and manage the contact group.

    Contact

    notification-http

    Click the name text box and select the contact created in Adding an HTTP/HTTPS Public Address for a Contact from the drop-down list. The notification protocols configured for the contact are automatically filled in.

  5. On the Create Contact Group page, click Create.

    After the contact is added to the contact group, the corresponding subscription endpoint will receive a subscription notification. The contact should access the link through the corresponding program or copy the link to a web browser to confirm the subscription. Then the contact can receive alarm notifications.

Creating a Notification Template

  1. Log in to the Cloud Eye console.
  1. In the navigation pane, choose Alarm Management > Alarm Notifications.
  2. Click the Notification Templates tab.
  3. Click Create. The Create Notification Template page is displayed.
  4. Configure the notification template information as prompted, as shown in Table 4.
    Table 4 Parameters for creating a notification template

    Parameter

    Example Value

    Description

    Name

    noticeTemplate-http(s)

    Name of the notification template. The system generates a random name, but you can change it. Enter 1 to 200 characters.

    Description

    -

    (Optional) Description of the alarm notification template.

    Protocol

    HTTP/HTTPS

    Select a notification method from the drop-down list.

    Notification Type

    Metric or Event

    Notification type of the notification content template.

    When you are configuring an alarm rule, the alarm type of the alarm rule determines the alarm type of the notification template. For example, for a metric alarm rule, you can select only Metric for this parameter. For more information about alarm types, see Overview.

    Format

    JSON

    Data format of the alarm notification content.

  5. Click Create. On the Notification Templates tab, you can view the new notification template whose Template Type is Custom.

Creating an Alarm Rule

Set monitoring metrics and alarm policies for target resources, and bind the alarm rules to the contact group and notification template.

Configure alarm rule parameters by referring to Creating an Alarm Rule and Notifications. The following table lists the alarm notification parameters.

Table 5 Alarm notification parameters

Parameter

Example Value

Description

Alarm Notifications

Enabled

Whether to send alarm notifications.

Notified By

Contact groups / Notification_Group-http

Notification method. You can select notification policies, contact groups, or topic subscriptions.

Notification Window

00:00–23:59 every day

Cloud Eye sends notifications only within the notification window.

Time Zone

(GMT+08:00) Beijing, Chongqing, Hong Kong, Urumqi, Kuala Lumpur, Singapore, Perth, Taipei, Irkutsk, Ulaanbaatar

Time zone for the alarm notification window. By default, it matches the time zone of the client, but can be manually configured.

Trigger Condition

Generated alarm and Cleared alarm

If you select a contact group or topic subscription for Notified By, you need to select the conditions for triggering alarm notifications.

  • If the alarm type is metric, you can select Generated alarm and Cleared alarm as the trigger conditions.
  • If the alarm type is event, you can only select Generated alarm.

Notification Template

noticeTemplate-http(s)

Notification content format. Alarm notifications are sent to contacts in the target format.

Viewing Alarm Notifications

When a metric or event triggers an alarm rule, the HTTP/HTTPS public address will receive an alarm notification encapsulated by SMN.

The following describes the fields in metric and event alarm notifications.

The following is an example of an alarm notification sent based on a custom metric notification template:
{
  "version": "v1",
  "data": {
    "Namespace": "Elastic Cloud Server",
    "DimensionName": "ECSs",
    "MetricName": "CPU Usage",
    "IsAlarm": true,
    "AlarmLevel": "Major",
    "Region": "CN North-Beijing4",
    "RegionId": "cn-north-4",
    "AlarmRuleName": "test-zcy",
    "AccountName": "RDS_test",
    "LastAlarmLevel": "Warning",
    "ResourceID": "853f8ead-428e-4c54-babc-f1bdae6d34a0",
    "PrivateIP": "10.0.0.39",
    "EPName": "default",
    "ResourceName": "ecs-hce330-test",
    "PrivateIPV6": "2407:c080:11f0:1115:490e:36fe:ba94:a410",
    "PublicIP": "100.85.113.106",
    "CurrentData": "100.00 %",
    "Count": 1,
    "IsOriginalValue": true,
    "Filter": "Raw data",
    "ComparisonOperator": ">=",
    "Value": "0%",
    "AlarmTime": "2025/11/17 16:39:42 GMT+08:00",
    "AlarmDesc": "test",
    "AlarmRecordID": "ah17223968140068KqpEA3NP",
    "ResourceDimensionInfos": [
      {
        "MetricName": "CPU Usage",
        "DimensionInfos": [
          {
            "Name": " ECS,"
            "Value": "853f8ead-428e-4c54-babc-f1bdae6d34a0"
          }
        ]
      }
    ],
    "AlarmNotificationType": "Metric",
    "Unit": "%",
    "ResourceTags": "_sys_type_hcss_x,test=test",
    "AlarmDurationTime": "0"
  }
}
Table 6 Metric alarm notification fields

Field

Type

Description

Namespace

String

Cloud service name.

DimensionName

String

Dimension name.

MetricName

String

Metric name.

IsAlarm

Boolean

Alarm triggering condition, indicating whether an alarm is generated.

  • true: An alarm is generated.
  • false: No alarm is generated.

AlarmLevel

String

Alarm severity. The value can be Critical, Major, Minor, or Warning.

Region

String

Region name, for example, CN North-Beijing4.

RegionId

String

Region ID, for example, cn-north-4.

AlarmRuleName

String

Alarm rule name.

AccountName

String

Account name.

LastAlarmLevel

String

Severity of the last alarm. The value can be Critical, Major, Minor, or Warning.

When a metric has several thresholds and the metric data triggers them, the alarm severity updates and this parameter appears in the notification.

ResourceID

String

Resource ID, that is, the dimension value. If there are multiple levels of dimensions, the names and values of all dimensions are displayed.

PrivateIP

String

Private IP address.

EPName

String

Name of the enterprise project to which the resource belongs.

ResourceName

String

Resource name.

PrivateIPV6

String

Private IPv6 address. Currently, only ECSs support this field.

PublicIP

String

Public IP address.

CurrentData

String

Metric value that triggers the alarm.

Count

Integer

Number of consecutive alarm triggers.

IsOriginalValue

Boolean

Whether the metric configured in the alarm policy uses the raw data.

  • true: The metric data is the raw data.
  • false: The metric data is the aggregated data.

Filter

String

Metric value type. The options are average value, variance value, minimum value, maximum value, sum value, and raw data.

ComparisonOperator

String

Comparison between the metric value and the threshold. The comparison operators include >, >=, <, <=, =, !=, cycle_increase (period-on-period increase), cycle_decrease (period-on-period decrease), and cycle_wave (period-on-period fluctuation).

Value

String

Value defined in the alarm rule.

AlarmTime

String

Time when the alarm is generated.

AlarmDesc

String

Description of the alarm rule.

AlarmRecordID

String

Alarm record ID.

ResourceDimensionInfos

Array of objects

Resource dimension information. For details, see Table 7.

AlarmNotificationType

String

Alarm notification type. The value can be Metric or Event.

Unit

String

Original unit of the metric.

ResourceTags

String

Resource tags.

AlarmDurationTime

String

Alarm duration.

Table 7 Resource dimension information

Field

Type

Description

MetricName

String

Metric name.

DimensionInfos

Array of objects

Dimension information. For details, see Table 8.

Table 8 Dimension information

Field

Type

Description

Name

String

Dimension name.

Value

String

Dimension value.

The following is an example of an alarm notification sent based on a custom event notification template:
{
  "version": "v1",
  "data": {
    "PrivateIPV6": "2407:c080:11f0:1115:490e:36fe:ba94:a410",
    "AlarmNotificationType": "Event",
    "AccountName": "RDS_test",
    "Namespace": "Elastic Cloud Server",
    "ResourceName": "ecs-abc-test",
    "ResourceTags": "_sys_type_hcss_x,test=test",
    "MetricName": "VM Restart",
    "IsAlarm": true,
    "IsCycleTrigger": false,
    "AlarmLevel": "Major",
    "Region": "CN North-Beijing4",
    "RegionId": "cn-north-4",
    "ResourceID": "7eb14e5d-8a79-4c94-8f8e-8f5467142490",
    "PrivateIP": "172.20.1.188",
    "PublicIP": "100.85.113.106",
    "EPName": "default",
    "AlarmRecordID": "ah260110T172316SmCFRcx7X",
    "AlarmRuleName": "alarm-VM Restart-abc-adafhads",
    "Filter": "Avg.",
    "ComparisonOperator": ">=",
    "AlarmDesc": "desc-test",
    "IsOriginalValue": false,
    "Count": 1,
    "AlarmTime": "2025/11/17 17:28:37 GMT+08:00",
    "ShowImpactAndSolution": true,
    "ImpactScope": "The VM is restarted.",
    "RecommendedSolution": "Check whether services are recovered."
    "DataPointTime": [
      "2025/11/17 17:28:35 GMT+08:00"
    ],
    "MonitoringRange": "Specified resources"
  }
}
Table 9 Event alarm notification fields

Field

Type

Description

PrivateIPV6

String

Private IPv6 address. Currently, only ECSs support this field.

AlarmNotificationType

String

Alarm notification type. The value can be Metric or Event.

AccountName

String

Account name.

Namespace

String

Cloud service name.

ResourceName

String

Resource name.

ResourceTags

String

Resource tags.

MetricName

String

Event name.

IsAlarm

Boolean

Alarm triggering condition, indicating whether an alarm is generated.

  • true: An alarm is generated.
  • false: No alarm is generated.

IsCycleTrigger

Boolean

Whether to continuously trigger alarms.

AlarmLevel

String

Alarm severity, which can be critical, major, minor, or warning.

Region

String

Region name, for example, CN North-Beijing4.

RegionId

String

Region ID, for example, cn-north-4.

ResourceID

String

Resource ID, that is, the dimension value. If there are multiple levels of dimensions, the names and values of all dimensions are displayed.

PrivateIP

String

Private IP address.

PublicIP

String

Public IP address.

EPName

String

Name of the enterprise project to which the resource belongs.

AlarmRecordID

String

Alarm record ID.

AlarmRuleName

String

Alarm rule name.

Filter

String

This field has no actual meaning for event alarms.

ComparisonOperator

String

This field has no actual meaning for event alarms. The default value is >=.

AlarmDesc

String

Description of the alarm rule.

IsOriginalValue

Boolean

Whether the metric configured in the alarm policy uses the raw data.

  • true: The metric data is the raw data.
  • false: The metric data is the aggregated data.

Count

Integer

Number of consecutive alarm triggers.

AlarmTime

String

Time when the alarm is generated.

ShowImpactAndSolution

Boolean

Whether the event impact and solution have values.

  • true: The event impact and solution have values.
  • false: The event impact and solution are empty.

ImpactScope

String

Event impact. Currently, only some interconnected cloud services support this field.

RecommendedSolution

String

Solution. Currently, only some interconnected cloud services support this field.

DataPointTime

Array of strings

Time when the event occurred. If the trigger type of the alarm policy in the event alarm rule is cumulative, the time of each event occurrence is displayed.

MonitoringRange

String

Monitoring scope. The value can be Specific resources, All resources, or Resource groups.