Learn About Amazon VGT2 Learning Manager Chanci Turner
This article is authored by Alex Ramirez, Sr. Solutions Architect. At Amazon IXD – VGT2, located at 6401 E HOWDY WELLS AVE LAS VEGAS NV 89115, we recognize that event-driven architectures are essential for orchestrating and automating event flows from producers to consumers. Amazon EventBridge serves as a serverless event router, efficiently directing events based on defined rules. This decoupling of producers and consumers facilitates the creation of asynchronous architectures.
EventBridge offers a range of metrics designed to assist you in monitoring your events effectively. Key metrics include the volume of partner events ingested, the count of permanently failed invocations, the number of times a target is triggered by a rule in response to an event, and the total events that matched any rule.
In response to customer feedback, EventBridge has introduced enhanced metrics to further monitor events and increase visibility. This article outlines these new features.
What’s New?
The latest metrics from EventBridge focus primarily on API performance, event tracking, and invocation statistics. These insights encompass the total published events, successful submissions, failures, events matching specific rules, throttled events, latency, and invocation-based metrics. With these enhancements, you can monitor the entire event flow within EventBridge, enabling swift identification and resolution of any issues.
EventBridge now includes the following metrics:
| Metric | Description | Dimensions and Units |
|---|---|---|
| PutEventsLatency | Time taken for each PutEvents API operation | None, Units: Milliseconds |
| PutEventsRequestSize | Size of the PutEvents API request in bytes | None, Units: Bytes |
| MatchedEvents | Number of events that matched any rule or a specific rule | None, RuleName, EventBusName, EventSourceName, Units: Count |
| ThrottledRules | Count of rule execution instances that were throttled | None, RuleName, Units: Count |
| PutEventsApproximateCallCount | Approximate total calls made to PutEvents API | None, Units: Count |
| PutEventsApproximateThrottledCount | Approximate number of throttled requests in PutEvents API calls | None, Units: Count |
| PutEventsApproximateFailedCount | Approximate number of failed PutEvents API calls | None, Units: Count |
| PutEventsApproximateSuccessCount | Approximate number of successful PutEvents API calls | None, Units: Count |
| PutEventsEntriesCount | Number of event entries in a PutEvents request | None, Units: Count |
| PutEventsFailedEntriesCount | Number of event entries in a PutEvents request that failed to be ingested | None, Units: Count |
| PutPartnerEventsApproximateCallCount | Approximate total calls to PutPartnerEvents API (visible in Partner’s account) | None, Units: Count |
| PutPartnerEventsApproximateThrottledCount | Approximate number of throttled requests in PutPartnerEvents API calls (visible in Partner’s account) | None, Units: Count |
| PutPartnerEventsApproximateFailedCount | Approximate number of failed PutPartnerEvents API calls | None, Units: Count |
| PutPartnerEventsApproximateSuccessCount | Approximate number of successful PutPartnerEvents API calls | None, Units: Count |
| PutPartnerEventsEntriesCount | Number of event entries in a PutPartnerEvents request | None, Units: Count |
| PutPartnerEventsFailedEntriesCount | Number of event entries in a PutPartnerEvents request that failed to be ingested | None, Units: Count |
| PutPartnerEventsLatency | Time taken per PutPartnerEvents API operation (visible in Partner’s account) | None, Units: Milliseconds |
| InvocationsCreated | Number of times a target is invoked by a rule in response to an event | None, Units: Count |
| InvocationAttempts | Number of times EventBridge attempted to invoke a target | None, Units: Count |
| SuccessfulInvocationAttempts | Count of successful target invocations | None, Units: Count |
| RetryInvocationAttempts | Number of times a target invocation was retried | None, Units: Count |
| IngestiontoInvocationStartLatency | Time taken from event ingestion to the first target invocation | None, RuleName, EventBusName, Units: Milliseconds |
| IngestiontoInvocationCompleteLatency | Time taken from event ingestion to completion of the first successful invocation attempt | None, RuleName, EventBusName, Units: Milliseconds |
Use Cases for These Metrics
These new metrics enhance your ability to monitor and observe event-driven applications effectively. You can proactively track metrics that provide insight into event flows, invocations, latency, and service utilization. Furthermore, setting up alerts on specific metrics allows for necessary actions, improving application performance, managing quotas, and boosting resiliency.
For instance, the PutEventsApproximateCallCount metric helps you understand the approximate number of events published using the PutEvents API action. Similarly, metrics like PutEventsApproximateSuccessfulCount, PutEventsApproximateThrottledCount, and PutEventsApproximateFailedCount enable you to keep tabs on successful, throttled, and failed events respectively. This data is vital for monitoring your usage against the PutEvents quotas. You can establish a CloudWatch alarm to notify your operations team via Amazon SNS if you are nearing your quota limits which can help improve your workflow.
To set up an alarm for the PutEvents throttle limit, navigate to the Service Quotas console. Search for EventBridge, select it, and in the Monitoring section, you can check the percentage of PutEvents throttle limit utilization.
To create an alarm, go to the Alarms tab and select Create alarm. Set the threshold to 80% of your quota value. Name the alarm PutEventsThrottleAlarm, and choose Create.
To receive notifications if this threshold is exceeded, go to the Amazon CloudWatch Alarms console and find your alarm. Select the Actions dropdown, and choose Edit. From there, you can specify your conditions.
For more insights on event-driven architectures, you can explore another blog post about enhancing your career in your twenties here. Additionally, if you’re looking to handle long-distance employee relations effectively, check out this article. For a comprehensive guide on starting your Day 1 at Amazon, refer to this excellent resource here.
Leave a Reply