Features

Events and Event Sources

Events are data that complies with specific specifications. Events that event sources publish to EG must comply with the CloudEvents specification.

Event sources are applications that produce events. EG supports the following event sources:

• Huawei Cloud service: Elastic Cloud Server (ECS), Object Storage Service (OBS), Cloud Container Engine (CCE), and other services
• Custom
  • Custom applications: connecting to EG via SDKs
  • DMS for RabbitMQ and DMS for RocketMQ

For details, see Events, Cloud Service Event Source, and Creating a Custom Event Source.

Event Channel

Event channels receive events from event sources.

EG supports the following event channels:

• Cloud service: A channel automatically created by EG to receive events from cloud services. This channel cannot be modified. Events generated by cloud service event sources can only be published to this channel.
• Custom: Channels you create to receive events from custom sources.

For details, see Event Channels.

Event Targets

Event targets are destinations that receive and process events. EG supports the following event targets:

• Huawei Cloud service: FunctionGraph and DMS for Kafka are supported.
• Custom: HTTP and HTTPS Webhooks
  

  Events cannot be delivered across accounts.

Event Subscriptions

Subscriptions bind event sources, channels, and targets. Events of sources are routed to targets based on specified rules.

For details, see Event Subscriptions.

Professional Event Streams

Professional event streams provide easy-to-use, stable, and efficient data pipelines for real-time synchronization across systems. They make data flow between middleware simple, greatly reducing data transfer costs. They are suitable for middleware data migration, backup, and disaster recovery in cloud migration, cross-cloud, and cross-region scenarios.

For details, see Professional Event Streams.

Event Rules

Event rules define how to filter and transform events.

• Filter: By configuring filter rules in a subscription, specify what events will be routed to the relevant target.
• Transform: By configuring the transform type in a subscription, determine how to transform CloudEvents-compliant events for the relevant target.

For details, see Event Rules.

Event Processing

EG provides the following event processing capabilities:

• Transfer
• Filtering
• Routing
  

  EG processes each event separately. This means that the event processing order cannot be guaranteed, and in some cases, an event may be passed multiple times. Therefore, event processing programs must be idempotent.

Network Management

You can manage your connections and endpoints.

• Connections: used to connect to Webhooks
• Endpoints: used to push custom events

For details, see Connections and Endpoints.

Event Monitoring

EG monitors event subscriptions and channels, and allows you to query event access and delivery information.

For details, see EG Metrics and Viewing Monitoring Data.

CTS Logs

Cloud Trace Service (CTS) records key operation events related to EG. The events can be used in various scenarios such as security analysis, compliance audit, resource tracing, and problem locating. After you enable CTS, the system starts to record EG operations.

For details, see EG Operations Recorded by CTS and Viewing CTS Traces in the Trace List.

API

EG provides REST APIs, which you can call using HTTPS.

For details, see API Reference.

SDK

EG provides the open-source CloudEvents SDK to simplify your development.

For details, see SDK Reference.