- Releases Notes and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- SQL Developer Guide
- Python Developer Guide
- ETL Developer Guide
- FAQ
- Contact Us
- Releases Notes and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- SQL Developer Guide
- Python Developer Guide
- ETL Developer Guide
- FAQ
- Contact Us
Stream Compute Service supports the detection and display of various events of a job, as detailed here. When an event occurs, it will be pushed to your EventBridge. On the Event Rule page in EventBridge, you can configure event matching rules to receive events from the backend of Stream Compute Service.
At present, EventBridge supports the following receiving channels free of charge: SMS, call, Email, Message Center, WeCom bot, and webhook.
Note
Job events in all regions will be reported to the event bus named "default" in EventBridge in Guangzhou. If a different region or event bus is set when an event rule is configured, event push will fail.
For an account, please do not send more than 1,000 messages within 24 hours to avoid failure to receive alarms after the limit is exceeded.
Viewing job alarm policies
1. On the Event Rule page in EventBridge, select Guangzhou as the region to view all configured rules.
2. Click Edit on the right of a rule to view its details, such as the related Tencent Cloud service and delivery method.
Adding a job alarm policy
1. On the Event Rule page in EventBridge, select Guangzhou as the region, and click Create.
2. On the Create event rule page, enter a rule name and rule description in the Basic information section. We recommend you use standard naming rules to identify rules.
3. In the Event matching section, set the mode to Template, the Tencent Cloud service to Stream Compute Service, and the event type to All Events or desired events (event names are case-sensitive). In addition, EventBridge supports flexible event patterns as described in Event Pattern. You can match event name and other fields by prefix, suffix, exclusion, or inclusion as needed.
Click Custom events or Edit match rule to set filter fields in the JSON script of the event matching rule.
Note: In the JSON script of the event matching rule, you can enter specific values following "data" to configure event alarms for jobs by job ID, job directory, job creator, cluster, workspace, or other dimensions, and the event alarms will be triggered accordingly. For more information, see Event Pattern.
The table below describes some common fields.
Field | Description | Example |
instanceId | The job ID | cql-xxxxxx |
folderId | The ID of the job directory | folder-xxxxxxxx |
creatorUin | The UIN of the job creator | 123456 |
clusterId | The ID of the cluster where the job resides | cluster-xxxxxxxx |
workSpaceId | The ID of the workspace where the job resides | space-xxxxxxxx |
For other fields, see Event sample of Event Type.
4. In the Delivery target section, set the trigger method to Notification message, and set recipients, notification period, delivery method, and webhook.
5. Select Enable event rules now, and click Complete to finish the rule creation.
Yes
No
Was this page helpful?