Emanating from CloudWatch Events, Amazon Web Services (AWS) launched EventBridge in July 2019: a serverless offering for event-driven architectures which now comprises of several components:

• Buses (brokers) with Rules to integrate consumers with event producers.
• Scheduling for fully managed invocations of one-time or recurring tasks.
• Pipes offering managed integrations between producers and consumers.

There is plenty of material available online explaining how EventBridge works. The product documentation serves as a valuable starting point. In this post, we will dive specifically into monitoring of EventBridge Rules.

We will start with an overview about how metrics work, after which we can explore current Rule metric offerings and identify their limitations. After we have covered a breadth of Rule metrics, we will conclude with proposed improvements which can deliver added value to customers.

How Rule Metrics Work

Consistent with other AWS services, EventBridge Rules offer CloudWatch metrics to observe performance. Some metrics may be broken down by one or more dimensions to review behaviour of specific…