tencent cloud


Alarm Policy Configuration

Last updated: 2022-07-21 15:16:28


    After EventBridge is enabled, it will automatically create a default Tencent Cloud service event bus in the Guangzhou region, and all services connected to it will automatically deliver events. You can also set event rules and delivery targets to configure an alarm link.

    Alarm Configuration Directions

    1. View the event list

    Log in to the EventBridge console, enter the default Tencent Cloud service event bus, and view the events of all connected Tencent Cloud services.

    The standard event format is as shown below:

      "subject":"${resource ID}",
      "time": 1615430559146,
              "IP":"something unnormal"

    The preceding fields are described as follows:

    Field Description Data Type
    specversion Event structure version (CloudEvents version, which is 1.0.2 currently). String
    id ID returned by PUT Event. String
    type Type of the event input through PUT Event. The standard format of a Tencent Cloud service alarm event is ${ProductName}:ErrorEvent:${EventType}, where colons are used to separate type fields. String
    source Event source (which is required for a Tencent Cloud service event and is the abbreviation of subject). The value is xxx.cloud.tencent by default for a Tencent Cloud service. String
    subject Event source details, which can be customized. QCS description such as qcs::dts:ap-guangzhou:appid/uin:xxx is used for a Tencent Cloud service by default. String
    timer Event time, which is a GMT+0 timestamp in milliseconds such as 1615430559146. Timestamp
    datacontenttype Data structure declaration. String
    region Region information. String
    status Alarm event status. Valid values: 1 (abnormal), 0 (resolved), - (stateless). String
    tags Resource tag. JSON
    data Details of the event input through PUT Event, which are customizable by the specific business. JSON

    2. Configure an alarm event rule

    Go to the Event Rule page, select the target event bus, and create an event rule under it to filter the events for which to configure alarm push.

    Taking CVM alarm configuration as an example, you can select a specified event alarm type as needed or all events.

    Sample alarm rules

    • Receiving all events
      Set "source" to "cvm.cloud.tencent", which indicates to receive and deliver all alarm events from CVM
    • Receiving specified events
      Only unreachable ping events from CVM are delivered. All other events will be discarded.

    • Receiving events from the specified instance
      Receive and deliver events of the CVM resource "ins-XXX". Other events are discarded. The format of "subject" varies for different event source. You can check the formats in the complete event delivered to CLS.


      Specifying multiple resources


    For more matching methods, see Event Pattern.

    3. Configure delivery targets

    In event alarm scenarios, we recommend you configure two delivery targets: CLS and Notification message.

    EventBridge provides a dedicated CLS log set for the default Tencent Cloud service event bus to deliver your alarm events, which helps you trace back delivered alarm events at any time.

    >? EventBridge offers a free tier of 1 GB per 30 days for storage in the dedicated log set to ensure that you can view and manage basic alarm events free of charge. Excessive storage will be billed according to the CLS billing rules. For more information, see Billing Overview.

    4. Test the configuration result

    After completing the configuration, return to the EventBridge console, select the bound event bus, and click Deliver Event. You can select a bound event rule template and click Deliver Event for test.


    The test template displays only the data field, while other fields are fixed and cannot be customized.

    After completing the configuration, you can view and configure the push of alarm events in the EventBridge console.

    Sample push content text

    Email content:

    ${ProductName} Alarm Notification
    Dear Tencent Cloud user,
    An alarm event occurred for ${ProductName} under your account (ID: ${1}, nickname: ${2}). Please check and resolve the issue in time.
    Alarm event: ${EventType}
    Alarmed service: ${ProductName}
    Alarmed resource: ${Subject}
    Alarm region: ${Region}
    Event occurrence time: ${Time}
    Event status: ${} ("error", "recovered", or "stateless")
    For more details, log in to the EventBridge console.

    Sample HTTP callback content:

    "sessionId": "xxxxxxxxxxxxxxxx",  // Event ID
    "alarmStatus": "1",//Event.Status
    "alarmType": "event",// The value is fixed, indicating an event alarm
    "alarmObjInfo": {
      "region": "sh",        // Event region
      "dimensions": {     // Additional description of the resource, which is not fixed and is determined by the respective service (CVM here)
         "unInstanceId": "ins-xxxxx",
         "objDetail": {
                     "deviceLanIp": "xxxx",
                     "deviceWanIp": ""
                     "uniqVpcId": "vpc-xxx"
           "deviceName": "xxx" 
    "alarmPolicyInfo": { // Alarm policy information, which is compatible with existing CM callbacks
         "policyName": "xxxx",  // EventBridge event rule name
           "conditions": {
               "productName": "cvm",                 // Alarmed service acronym
                "eventName": "guest_reboot",    // Alarm event type
                "alarmNotifyType": "", // It is left empty and is compatible with existing CM callbacks
                "alarmNotifyPeriod": ""  // It is left empty and is compatible with existing CM callbacks
    "additionalMsg": [{ // Additional information of the alarm event, which is determined by the alarm reporter (CVM here)
    "key": "alias",
    "value": "xxxx"
    }, {
    "key": "deviceLanIp",
    "value": "xxxx"
    }, {
    "key": "deviceWanIp",
    "value": ""
    }, {
    "key": "uniqVpcId",
    "value": ""
    "firstOccurTime": "2021-10-19 11:15:47", // Alarm time
    "durationTime": 0,  // Duration
    "recoverTime": "0"  // Recovery time
    Contact Us

    Contact our sales team or business advisors to help your business.

    Technical Support

    Open a ticket if you're looking for further assistance. Our Ticket is 7x24 avaliable.

    7x24 Phone Support