As an event delivery pipeline on the cloud, EventBridge only filters, routes, and distributes events. If you need to log or store events, you can configure CLS as the delivery target.
Permission Description
To ensure normal log viewing, your account must have at least the read-only permission QcloudCLSReadOnlyAccess
of CLS if you are using a sub-account. For how to use the root account to grant permissions for a sub-account, see Authorization Management. Feature Description
Currently, EventBridge supports two delivery methods: default logset delivery and custom logset delivery.
When creating a delivery target, if you do not specify the destination topic for log delivery, the default log delivery capability will be used. For default log delivery, EventBridge will activate the CLS service for you and deliver the function invocation logs to the log topic under the EventBridge's default logset. The EventBridge's default logset and log topic are prefixed with EB_logset
and EB_logtopic
respectively, and will be created automatically if they do not exist. Function invocation logs will be stored for 30 days by default, and you can view and manage them in the CLS console.
Billing Description
CLS is billed separately, and certain fees may incur. For details about the billing method, see CLS Billing Overview. When creating a delivery target, if you need to specify the destination log topic for log delivery, you can use the custom log delivery capability. Before using this capability, you need to make sure that the CLS service has been activated for your account.
Billing
CLS is billed separately. After a custom logset is bound, the fee deduction rule on the CLS side prevails. For more information, see Billing Overview. Configuration Instructions
1. View and manage logs
After creating a delivery target, you can choose Event Rule > Event Target to view the bound logset and log topic, and click the log topic to go to the CLS console to view and manage logs.
EventBridge's default logset is marked with "EB" in the CLS console. If you have requirements such as persistent event storage, perform further configuration and management in the CLS console.
2. Manage indexes
Log searching depends on the index configuration of the log topic. For the default logset, EventBridge automatically performs index configuration for you. Currently, the following index fields are supported:
Note:
If you select a custom logset, ensure that the logset is also configured with the following indexes. Otherwise, events cannot be queried on the CLS side after being delivered.
|
sourceType | text | N/A | No |
caller | text | N/A | No |
eventbusId | text | N/A | No |
status | text | N/A | No |
specversion | text | N/A | No |
id | text | N/A | No |
type | text | N/A | No |
source | text | N/A | No |
subject | text | N/A | No |
region | text | N/A | No |
datacontenttype | text | N/A | No |
tags | text | N/A | No |
data | text | N/A | No |
time | text | N/A | No |
Was this page helpful?