Help Center/ Cloud Trace Service/ Getting Started/ Configuring Key Event Notifications
Updated on 2023-11-24 GMT+08:00
View PDF
Share

Configuring Key Event Notifications

Scenarios

You can use this function for:
  • Real-time detection of high-risk operations (such as VM restart and security configuration changes), cost-sensitive operations (such as creating and deleting expensive resources), and service-sensitive operations (such as network configuration changes).
  • Detection of operations such as login of users with admin-level permissions or operations performed by users who do not have the required permissions.
  • Connection with your own audit system: You can synchronize all audit logs to your audit system in real time to analyze the API calling success rate, unauthorized operations, security, and costs.

Prerequisites

  • SMN sends key event notifications to subscribers. Before setting notifications, you need to know how to create topics and add subscriptions on the SMN console.
  • You can create up to 100 key event notifications on CTS:
    • Specify key operations, users, and topics to customize notifications.
    • Complete key event notifications can be sent to notification topics.
  • If CTS and Cloud Eye use the same message topic, they can receive messages from the same terminal but with different content.
  • You can configure one key event notification for operations initiated by a maximum of 50 users in 10 user groups. For each key event notification, you can add users from different user groups, but cannot select multiple user groups at once.

Creating a Key Event Notification

  1. Log in to the management console.
  2. Click in the upper left corner and choose Management & Governance > Cloud Trace Service. The CTS console is displayed.
  3. In the navigation pane on the left, choose Key Event Notifications.

    The Key Event Notifications page is displayed.

  4. Click Create Key Event Notification. On the displayed page, specify required parameters.
  5. Enter a key event notification name.

    Notification Name: Identifies key event notifications. This parameter is mandatory. The name can contain up to 64 characters. Only letters, digits, and underscores (_) are allowed.

  6. Configure key operations.
    Select the operations that will trigger notifications. When a selected operation is performed, an SMN notification is sent immediately.
    • Operation Type: Select All or Custom.
      • All: This option is suitable if you have connected CTS to your own audit system. When All is chosen, you cannot deselect operations because all operations on all cloud services that have connected with CTS will trigger notifications. You are advised to use an SMN topic for which HTTPS is selected.
      • Custom: This option is suitable for enterprises that require detection of high-risk, cost-sensitive, service-sensitive, and unauthorized operations. You can connect CTS to your own audit system for log analysis.

        Customize the operations that will trigger notifications. Up to 1000 operations of 100 services can be added for each notification. For details, see Supported Services and Operations.

    • Advanced Filter: You can set an advanced filter to specify the operations that will trigger notifications. Operations can be filtered by fields api_version, code, trace_rating, trace_type, resource_id, and resource_name. Up to six filter conditions can be set. When you configure multiple conditions, specify whether an operation is considered a match when all conditions are met (AND) or any of the conditions are met (OR).
  7. Configure users.

    SMN messages will be sent to subscribers when the specified users perform key operations.

    • If you select All users, SMN will notify subscribers of key operations initiated by all users.
    • If you select Specified users, SMN will notify subscribers of key operations initiated by your specified users. You can configure key event notifications on operations for up to 50 users in 10 user groups. For each notification, you can select multiple users in the same user group.
  8. Configure an SMN topic.
    • When Yes is selected for Send Notification:
      • Create a cloud service agency.: (Mandatory) If you select this check box, CTS automatically creates a cloud service agency when you create a key event notification. The agency authorizes you to use SMN.
      • SMN Topic: You can select an existing topic or click SMN to create one on the SMN console.
    • If you do not want to send notifications, no further action is required.
  9. Click OK.

Managing Key Event Notifications

After you create a key event notification, you can view its name, status, template, and SMN topic in the notification list and delete it as required.

  1. Log in to the management console.
  2. Click in the upper left corner and choose Management & Governance > Cloud Trace Service. The CTS console is displayed.
  3. Choose Key Event Notifications in the navigation pane on the left. On the displayed page, perform the following operations as required. For details, see Table 1.

    Table 1 Related operations

    Operation

    Description

    Viewing a key event notification

    Click the notification name to view the operation list and user list details of the notification.

    Enable/Disable a key event notification

    Click Enable or Disable in the Operation column.

    NOTE:

    CTS can trigger key event notifications only after SMN is configured.

    Modifying a key event notification

    Click Modify in the Operation column to modify the configuration of the key event notification.

    Deleting a key event notification

    Click Delete in the Operation column.

    Searching for a notification

    In the search box above the list, you can search for notifications by notification name, status, template type, or SMN topic.

    Refreshing the key event notification list

    Click in the upper right corner.

    Configuring basic settings

    Click in the upper right corner to set table text wrapping, fixed operation column position, and custom columns.