Skip to content
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

New CloudWatch Cold Start Metrics #169

Merged
merged 1 commit into from
Jul 7, 2023
Merged

New CloudWatch Cold Start Metrics #169

merged 1 commit into from
Jul 7, 2023

Conversation

metaskills
Copy link
Member

@metaskills metaskills commented Jul 7, 2023

Optional and defaults to being turned off. Use config.cold_start_metrics = true to enable.

https://docs.aws.amazon.com/lambda/latest/dg/troubleshooting-invocation.html#

For functions using unreserved (on-demand) concurrency, Lambda may proactively initialize a function instance, even if there's no invocation. When this happens, you can observe an unexpected time gap between your function's initialization and invocation phases. This gap can appear similar to what you would observe using provisioned concurrency.

@metaskills metaskills merged commit f812aad into master Jul 7, 2023
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant