使用 AWS re:Post 即表示您同意 AWS re:Post 使用條款
AWS re:Postre:Post

Component health status for pinned lambda functions running in Greengrass v2

0

I'm exploring possibilities for implementing a health monitoring mechanism for a long running (pinned) lambda function running on Greengrass v2 based on EventBridge as documented

Assuming the deployment of the lambda component has been successful and the failure (e.g. the Java application terminating with a non zero exit code) occurs after an extended period of time, will I get any notifications about the lambda crashing?

After inspecting the detailed component status codes it's still unclear to me.

主題
物聯網 (IoT)無伺服器運算
標籤
AWS IoT GreengrassAWS IoT CoreAWS Lambda
語言
English
George H
已提問 4 個月前檢視次數 227 次
1 個回答
1
已接受的答案

Hello,

Lambda components are different, there is no component status code for lambda. The lambda components have a health check ping, (1 min by default). If lambda manager does not receive that ping, then it transition lambda to ERRORED state, and Greengrass will send notifications if you set up the event bridge and monitor the component status change. Greengrass will retry the component 3 times within 1 hour. If it continues to fail, it will be marked as broken and you will receive an event for the broken component.

AWS
yitingb
已回答 4 個月前
  • George H
    4 個月前

    Thank you for the answer. Is there a way to control the ping mechanism, number and intervals for retry, etc? Can you please link the documentation?

  • yitingb
    4 個月前

    Yes, to control the ping mechanism, please refer to Status timeout for console and statusTimeoutInSeconds for cli step 1.6.c. We recommend to set the status timeout greater than 10s.

    You can't customize retry number and intervals. For other Greengrass device configuration, please refer to this document, for recipe reference, please refer to this document

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋，同時有助於提問者的專業成長。

回答問題指南

相關內容