You need to enable JavaScript to run this app.
Torch Object Storage

Torch Object Storage

Copy page
Download PDF
Event monitoring
Creating event rules
Copy page
Download PDF
Creating event rules
To quickly identify any abnormal occurrences, you can set up alert rules to receive notifications through the specified channel when certain events occur in your TOS bucket. This topic explains how to do that.​
Prerequisites​
You have either created contracts and associated them with a contact group, or created a callback URL. For more information, see Creating contacts and Create a callback URL.​
Steps​
  1. Log in to the Cloud Monitor console.​
  1. In the left navigation pane, select Event Center > Event rule.​
  1. On the Event rule page, click Create event rule.​
  1. On the Create event rule page, configure the following parameters.​
  • ​
    Parameter​
    Description​
    Name​
    Enter the name of the event rule. Naming rules:​
    • The rule name must be between 1 and 128 characters long.​
    • The rule name cannot start with a number or a hyphen (-).​
    Description​
    Provide additional information about the event rule.​
    Resource type​
    Select object storage.​
    Event name​
    Select the event types you want to monitor. For a list of supported event types for TOS, see Throttling event metrics.​
    Severity level​
    Specify the severity level of the event. The options are Critical, Warning, and Notification.​
    Project selection​
    Select the project(s) to which the resources that you want to monitor belong. The options are All projects or Partial projects.​
    Match by event details​
    (Optional) Use this to further filter the alert scope based on the TOS event's detailed fields. Click Add to configure matching conditions using fields after data., such as "bucket name", "object name", "request source", or "error code".​
    For example, to receive alerts only for a particular bucket, set data.bucketName = example-bucket.​
    Notification policy​
    Select a notification policy after an alert is triggered. A notification policy specifies who will receive notifications and how they will be delivered. Supported notification methods include phone, SMS, email, Feishu, WeCom, DingTalk, Slack, callback URL, orchestration, Torch Log Service, and Message Queue for Kafka. If the default policy does not meet your needs, you can create a custom notification policy. For more information, see Creating a notification policy.​
    ​
  1. Once you have finished configuring, click Confirm.​
  • Event rules are enabled by default once created. You can change an event rule's status where necessary. For instructions, see Managing event rules.​
​
​
Last updated: 2026.09.16 10:47:11