AWS EventBridge Integration
Monitor event bus throughput, rule match rates, and DLQ depth across your AWS EventBridge infrastructure. Detect silent rule match failures and target delivery errors before they break your event-driven workflows.
How It Works
Connect via CloudWatch Metric Streams
Deploy the TigerOps CloudWatch Metric Stream using the provided CloudFormation template. It creates a Kinesis Firehose stream that forwards EventBridge CloudWatch metrics to your TigerOps endpoint in near real-time.
Configure IAM & Event Bus Scope
Attach the TigerOps IAM role with CloudWatch read permissions. Specify the event buses to monitor — custom, partner, and the default bus. The integration auto-discovers all rules and targets per bus.
Set Rule Match & DLQ Thresholds
Define per-rule match rate expectations and DLQ depth limits. TigerOps alerts when rule match rates drop unexpectedly (event pattern mismatch) or DLQ depth grows, indicating failed target invocations.
Correlate with Target Services
TigerOps links EventBridge delivery failures with target Lambda error rates, SQS queue depths, API Gateway 5xx rates, and Step Functions execution failures for end-to-end event flow visibility.
What You Get Out of the Box
Event Bus Throughput Monitoring
Track events ingested, matched, and throttled per event bus. Monitor custom event bus PutEvents rates against your account-level throughput limits and alert before throttling impacts event routing.
Rule Match Rate Analysis
Per-rule MatchedEvents and InvocationsCount metrics with trend analysis. Detect when a rule stops matching events — indicating upstream producer changes broke the event pattern — before downstream consumers notice.
Dead Letter Queue Depth Tracking
Monitor the DLQ SQS queue depth for each EventBridge rule target. Alert when failed target invocations accumulate in the DLQ and correlate with target service health metrics.
Target Invocation Success Rates
Track SuccessfulInvocations and FailedInvocations per rule target. Identify which targets (Lambda, SQS, Step Functions, API destinations) are consistently failing and correlate with service-level metrics.
Throttle & Limit Monitoring
Track ThrottledRules counts and PutEvents throttle metrics. EventBridge account limits (PutEvents TPS, rules per bus) are tracked against your usage so you can request limit increases proactively.
AI Root Cause Analysis
When EventBridge delivery failures spike, TigerOps AI correlates target Lambda cold start rates, SQS visibility timeout issues, downstream database latency, and IAM permission errors to identify the root cause.
CloudFormation Deployment
Deploy the TigerOps CloudWatch Metric Stream to your AWS account with the CLI or CloudFormation console.
# Deploy TigerOps CloudWatch Metric Stream for EventBridge
aws cloudformation deploy \
--template-url https://tigerops-cfn.s3.amazonaws.com/metric-stream.yaml \
--stack-name tigerops-eventbridge-monitoring \
--capabilities CAPABILITY_IAM \
--parameter-overrides \
TigerOpsApiKey="${TIGEROPS_API_KEY}" \
TigerOpsEndpoint="https://ingest.atatus.net/cloudwatch/v1/stream" \
# Namespace filter — include only EventBridge metrics
IncludeNamespaces="AWS/Events" \
# Optional: also include Lambda/SQS for target correlation
AdditionalNamespaces="AWS/Lambda,AWS/SQS,AWS/States"
# After deployment, verify the Metric Stream is delivering:
aws cloudwatch describe-metric-streams \
--query "Entries[?Name=='tigerops-eventbridge-stream'].State"
# Expected output: ["RUNNING"]
# TigerOps will begin receiving metrics within 60 seconds:
# - Events.Invocations (per rule)
# - Events.MatchedEvents (per rule)
# - Events.FailedInvocations (per rule)
# - Events.ThrottledRules (per bus)
# - Events.DeadLetterInvocations (per rule)
# - Events.InvocationAttempts (per rule)Common Questions
How does TigerOps collect EventBridge metrics from AWS?
TigerOps uses AWS CloudWatch Metric Streams with a Kinesis Data Firehose delivery stream. This approach delivers metrics with sub-minute latency — much faster than the standard 5-minute CloudWatch polling interval. A CloudFormation template provisions everything automatically.
Does TigerOps support monitoring EventBridge Pipes?
Yes. EventBridge Pipes metrics — including ExecutionThrottled, ExecutionsFailed, and ExecutionStarted counts — are captured via CloudWatch Metric Streams. You can alert on pipe execution failure rates and correlate with source SQS/DynamoDB and target Lambda metrics.
Can TigerOps monitor partner event buses from SaaS providers?
Yes. Partner event buses (e.g., from AWS partners like Zendesk, Datadog, or Auth0) appear as distinct event buses in CloudWatch and are monitored identically to custom event buses. Rule match rates and DLQ metrics are tracked per partner bus.
How do I detect when an EventBridge event pattern stops matching?
TigerOps tracks the MatchedEvents metric per rule. If a rule's matched event count drops to zero while the source event bus continues to receive events, TigerOps fires a "rule match dropout" alert — indicating that upstream event producers changed their schema and broke the pattern.
Does TigerOps support multi-account EventBridge monitoring?
Yes. Deploy the TigerOps CloudFormation stack in each AWS account. TigerOps consolidates metrics across accounts with an account_id label so you can view cross-account event bus health in unified dashboards and set account-spanning alerts.
Stop Discovering EventBridge Routing Failures Hours Later
Rule match dropout alerts, DLQ depth monitoring, and target failure correlation. Deploy via CloudFormation in minutes.