- 最新
- 投票最多
- 评论最多
Hi,
as per https://docs.aws.amazon.com/glue/latest/dg/automating-awsglue-with-cloudwatch-events.html, FAILED is available for Glue Crawler State Change
Events for "detail-type":"Glue Job State Change" are generated for SUCCEEDED, FAILED, TIMEOUT
, and STOPPED.
You may want to follow the guidance of https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-troubleshooting.html to investigate your current issue.
This article also shows how to trigger jobs based on your "Glue Job State Change" event: https://repost.aws/knowledge-center/glue-cross-account-job-trigger You may compare your own settings with this example.
Best,
Didier
That is for Glue Job. The Question refers to the "Glue Crawler State Change".
You're right: apologies. "Failed" is also fine for "Glue Crawler State Change" as per same page. So, the troubleshooting guide link also applies in your case,
I have the same requirement in my environment and the above code works perfectly fine for me. If "Started" and "Succeeded" states works fine for you then you can follow these steps to troubleshoot -
- Check if Eventbridge rule is getting triggered - from the monitoring tab in your eventbridge rule, see if your rule has been invoked. If it is invoked then lambda has received the event. If not eventbridge has not received the config change.
- Check your permissions - If you are using custom event bus check its permissions
- GO with aws config - develop the event pattern as source as aws config
Thanks for the reply, 1. The Eventbridge rule is triggered for "Started" and "Succeeded" but not for "Failed" 2. I am currently using the default event bus 3. Developed the event pattern as aws config and still running into the same issue where "Failed" event is not invoking the defined rule
相关内容
- AWS 官方已更新 2 年前
- AWS 官方已更新 1 年前
- AWS 官方已更新 8 个月前
Thanks for the feedback everyone, upon further testing I've noticed that certain error sends the failed event and certain does not.
e.g.
For the testing the crawler configurations are exactly the same, the only difference is the connection used. The first connection uses a valid JDBC URL but incorrect database name. The second connection uses an invalid JDB URL.