- Newest
- Most votes
- Most comments
I've looked at your EventBridge rule configuration for the Glue Crawler events, and your pattern actually looks correct:
{
"detail": {
"crawlerName": [ "abc_crawler" ],
"state": [ "Succeeded" ]
},
"detail-type": [ "Glue Crawler State Change" ],
"source": [ "aws.glue" ]
}
This matches the expected format for capturing Glue Crawler state changes. Since the format seems right, we need to look at the metrics to understand where things might be breaking down.
Could you check the following EventBridge metrics to help us narrow down the issue:
- Invocations
- MatchedEvents
- SuccessfulInvocationAttempts
- TriggeredRules
If these metrics show activity, then the events are reaching EventBridge and being processed to the target. In that case, we'd need to look at your Lambda function to see why it's not completing the workflow.
On the other hand, if you're seeing FailedInvocations in the metrics, the issue is likely on the source side - possibly with how the Glue Crawler is emitting events.
One thing that might help troubleshoot is configuring a Dead Letter Queue (DLQ) for your target. You can do this under the Additional Parameters section when configuring your target. This would capture any events that couldn't be processed successfully and give us more insight.
Let me know what you find, and we can take it from there.
Relevant content
asked 3 years ago
asked 3 years ago
asked 2 years ago
- AWS OFFICIALUpdated 5 years ago
