-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make invocation timeouts visible in Elastic APM #118
Comments
I have started to run into this and took a while for me to figure out what was happening. |
@SHolzhauer thanks for your feedback on this issue. We have it on our radar, but might not be able to immediately prioritize it. |
My team needs this feature also, is there any progress? |
This has been solved from the Lambda extension side with #315, but it still requires the corresponding APM agents to support that new mode. The tracking issue for the agents is: elastic/apm#753 |
When a lambda invocation times out, then in most cases the APM agents won't be able to finalize and send the corresponding transaction to the extension and APM server. As a consequence, lambda function invocations that time out are not visible in APM at all. However, seeing timed out invocations in APM is essential as it is an important indicator that something is wrong with a function or it is too slow.
The lambda runtime notifies external extensions with the
shutdown
event in case of a timeout. This mechanism could be used by the APM extension to generate and send an artificial transaction (with afailure
state and additional information on the timeout). In this way APM would provide information on timed out invocations.The text was updated successfully, but these errors were encountered: