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.

질문됨 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달 전
  • 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?

  • 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

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

질문 답변하기에 대한 가이드라인

관련 콘텐츠