tencent cloud

Tencent Cloud Observability Platform

Release Notes and Announcements
Release Notes
Product Introduction
Overview
Strengths
Basic Features
Basic Concepts
Use Cases
Use Limits
Purchase Guide
Tencent Cloud Product Monitoring
Application Performance Management
Mobile App Performance Monitoring
Real User Monitoring
Cloud Automated Testing
Prometheus Monitoring
Grafana
EventBridge
PTS
Quick Start
Monitoring Overview
Instance Group
Tencent Cloud Product Monitoring
Application Performance Management
Real User Monitoring
Cloud Automated Testing
Performance Testing Service
Prometheus Getting Started
Grafana
Dashboard Creation
EventBridge
Alarm Service
Cloud Product Monitoring
Tencent Cloud Service Metrics
Operation Guide
CVM Agents
Cloud Product Monitoring Integration with Grafana
Troubleshooting
Practical Tutorial
Application Performance Management
Product Introduction
Access Guide
Operation Guide
Practical Tutorial
Parameter Information
FAQs
Mobile App Performance Monitoring
Overview
Operation Guide
Access Guide
Practical Tutorial
Tencent Cloud Real User Monitoring
Product Introduction
Operation Guide
Connection Guide
FAQs
Cloud Automated Testing
Product Introduction
Operation Guide
FAQs
Performance Testing Service
Overview
Operation Guide
Practice Tutorial
JavaScript API List
FAQs
Prometheus Monitoring
Product Introduction
Access Guide
Operation Guide
Practical Tutorial
Terraform
FAQs
Grafana
Product Introduction
Operation Guide
Guide on Grafana Common Features
FAQs
Dashboard
Overview
Operation Guide
Alarm Management
Console Operation Guide
Troubleshooting
FAQs
EventBridge
Product Introduction
Operation Guide
Practical Tutorial
FAQs
Report Management
FAQs
General
Alarm Service
Concepts
Monitoring Charts
CVM Agents
Dynamic Alarm Threshold
CM Connection to Grafana
Documentation Guide
Related Agreements
Application Performance Management Service Level Agreement
APM Privacy Policy
APM Data Processing And Security Agreement
RUM Service Level Agreement
Mobile Performance Monitoring Service Level Agreement
Cloud Automated Testing Service Level Agreement
Prometheus Service Level Agreement
TCMG Service Level Agreements
PTS Service Level Agreement
PTS Use Limits
Cloud Monitor Service Level Agreement
API Documentation
History
Introduction
API Category
Making API Requests
Monitoring Data Query APIs
Alarm APIs
Legacy Alert APIs
Notification Template APIs
TMP APIs
Grafana Service APIs
Event Center APIs
TencentCloud Managed Service for Prometheus APIs
Monitoring APIs
Data Types
Error Codes
Glossary

Limits

PDF
Focus Mode
Font Size
Last updated: 2024-11-01 20:38:40
EventBridge has certain quota limits for each user account. This document describes such quota limits.

Quota Limits

The quota limits for each user account are as follows:
Content
Default Quota Limit
Maximum throughput of the PutEvents API per region
5,000 TPS
Maximum number of custom event buses per region
10
Maximum number of rules that can be bound to a custom event bus
10
Maximum number of rules that can be bound to a Tencent Cloud service event bus
200
Maximum number of targets that can be configured in an event rule
10
Maximum size of an event message body
64 KB
Maximum number of connectors supported by an event bus
10
Maximum number of events delivered to a target
2,000 events/day
Note:
EventBridge currently supports 10,000-level concurrency, which can effectively support scenarios with high concurrency demand such as ecommerce promotions and parallel processing of medical and biological data. To request a quota increase, please submit a ticket.
You can specify the relevant limits by scopes such as region and event bus. To request a quota increase, please submit a ticket.

Rules and Limitations

Event bus Event bus name: it can contain 2–60 letters, digits, underscores, and hyphens and must start with a letter and end with a digit or letter. Event bus description: it can contain up to 200 characters of any type.
Event rule Event rule name: it can contain 2–60 letters, digits, underscores, and hyphens and must start with a letter and end with a digit or letter. Event rule description: it can contain up to 200 characters of any type.
Connector Connector name: it can contain 2–60 letters, digits, underscores, and hyphens and must start with a letter and end with a digit or letter.

Deletion Exceptions

Event bus deletion: To delete an event bus, you need to delete all its trigger rules and connectors first; otherwise, the error message "An event rule/connector has been bound to this event bus. Please try again after deleting the bound event rule" will be displayed. After the event bus is deleted from the data flow, all corresponding resource information will also be deleted.
Event rule deletion: To delete an event rule, you need to delete all its targets first; otherwise, the error message "An event target has been bound to this event rule. Please try again after deleting the bound event target" will be displayed. After the event rule is deleted from the data flow, delivery of events related to the rule to the corresponding event bus will also stop.
Event target deletion: The component resources of the relevant delivery logic will be deleted from the data flow.
Connector deletion: The connector resources will be deleted from the data flow, and messages will no longer be delivered to the corresponding event bus.

Retrial upon Exceptions

EventBridge retries when the delivery of an event to a downstream target fails.

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback