AWS EventBridge Integration
Monitor event bus metrics, rule invocation counts, and dead-letter queue monitoring across your EventBridge event-driven architecture. Get AI-powered silent bus detection and failed invocation correlation.
How It Works
Create IAM Role for Metric Streams
Provision an IAM role with CloudWatch permissions scoped to the AWS/Events namespace. TigerOps uses this role to deliver EventBridge bus, rule, and DLQ metrics via Firehose.
Deploy CloudWatch Metric Streams
Run the TigerOps CloudFormation stack to stream the AWS/Events namespace. Event match counts, rule invocations, failed invocations, and DLQ metrics begin flowing immediately.
Configure Dead-Letter Queue Monitoring
Add SQS DLQ metrics to the Metric Stream filter alongside EventBridge metrics. TigerOps correlates failed EventBridge target invocations with DLQ depth increases automatically.
Set Rule Invocation Failure Alerts
Configure alerts on FailedInvocations per rule. TigerOps fires alerts when target invocation failures spike and identifies whether the failure is in a Lambda, SQS, or Step Functions target.
What You Get Out of the Box
Event Bus Metrics
MatchedEvents and TriggeredRules counts per custom and default event bus. Track event throughput trends and detect buses with unexpectedly high or low event volumes.
Rule Invocation Counts
Invocations per rule with success and failure breakdown. Identify which rules are firing most frequently and correlate rule activation spikes with upstream service events.
Dead-Letter Queue Monitoring
DLQ message counts, DLQ depth trends, and failed invocation rates per EventBridge rule. Alert when DLQ depth grows, indicating persistent target failures requiring investigation.
Failed Invocation Analysis
Failed target invocations broken down by target type (Lambda, SQS, SNS, Step Functions). Correlate EventBridge failures with downstream target service health metrics.
Event Bus Throttling Detection
ThrottledRules metric tracking when EventBridge rate limits are hit on a bus. Identify high-frequency event patterns that are causing bus throttling and impacting rule invocations.
AI Event Volume Anomaly Detection
TigerOps establishes per-bus and per-rule event volume baselines. Silent bus anomalies (zero events when activity is expected) trigger alerts that catch upstream producer failures early.
CloudFormation Stack for EventBridge Metric Streams
Deploy the TigerOps CloudFormation stack to stream EventBridge bus, rule, and DLQ metrics in minutes.
# TigerOps CloudFormation — EventBridge Metric Streams
# aws cloudformation deploy \
# --template-file tigerops-eventbridge-streams.yaml \
# --stack-name tigerops-eventbridge \
# --capabilities CAPABILITY_IAM
Parameters:
TigerOpsApiKey:
Type: String
NoEcho: true
Resources:
TigerOpsEventBridgeStream:
Type: AWS::CloudWatch::MetricStream
Properties:
Name: tigerops-eventbridge-stream
FirehoseArn: !GetAtt TigerOpsDeliveryStream.Arn
RoleArn: !GetAtt MetricStreamRole.Arn
OutputFormat: opentelemetry0.7
IncludeFilters:
- Namespace: AWS/Events
- Namespace: AWS/EventBridge/Pipes
- Namespace: AWS/Scheduler
TigerOpsDeliveryStream:
Type: AWS::KinesisFirehose::DeliveryStream
Properties:
HttpEndpointDestinationConfiguration:
EndpointConfiguration:
Url: https://ingest.atatus.net/api/v1/cloudwatch
AccessKey: !Ref TigerOpsApiKey
RequestConfiguration:
CommonAttributes:
- AttributeName: service
AttributeValue: eventbridge
RetryOptions:
DurationInSeconds: 60
# Critical alerts to configure in TigerOps:
# FailedInvocations > 0 for any rule → Immediate alert
# DeadLetterInvocations > 0 → Immediate alert
# MatchedEvents = 0 for bus during business hours → Silent bus alertCommon Questions
Which EventBridge metrics does TigerOps collect?
TigerOps collects all AWS/Events CloudWatch metrics including MatchedEvents, TriggeredRules, Invocations, FailedInvocations, ThrottledRules, and DeadLetterInvocations per event bus and rule dimensions.
Does TigerOps support EventBridge Pipes monitoring?
Yes. EventBridge Pipes publish metrics to the AWS/EventBridge/Pipes namespace. TigerOps includes this namespace in the Metric Stream and provides dedicated Pipes dashboards showing source polling rates, filter rates, enrichment latency, and target delivery rates.
Can TigerOps monitor EventBridge Scheduler invocations?
Yes. EventBridge Scheduler publishes InvocationAttempts, InvocationThrottleCount, and InvocationDroppedCount metrics. TigerOps tracks scheduler execution health and alerts on dropped invocations that indicate schedule capacity issues.
How does TigerOps detect when an event bus goes silent unexpectedly?
TigerOps uses absence-of-signal alerting based on historical event volume baselines. If a bus that normally receives hundreds of events per minute goes to zero, TigerOps fires a missing data alert within the configured detection window.
Does TigerOps support cross-account EventBridge monitoring?
Yes. EventBridge cross-account event buses can be monitored by deploying the TigerOps Metric Stream stack in each source account. TigerOps aggregates events from all accounts and lets you trace cross-account event flows when debugging distributed event-driven architectures.
Stop Discovering Silent EventBridge Buses Only When Downstream Systems Break
Event bus monitoring, DLQ alerting, and AI silent bus detection. Deploy in 5 minutes.