localstack.lambda.cold_start.duration
Cold start durationDimensions:None
Available on:Native (1)
Interface Metrics (1)
Native
Duration of Lambda cold start initialization in millisecondsDimensions:None
Technical Annotations (22)
Configuration Parameters (5)
LAMBDA_RUNTIME_ENVIRONMENT_TIMEOUTrecommended: 600LAMBDA_EXECUTORrecommended: local or docker-reuselatencyrecommended: 5000LAMBDA_DOCKER_NETWORKrecommended: remove entirelyAWS_ENDPOINT_URLError Signatures (4)
timed out during startup. Check for errors during the startup of your Lambda function and consider increasing the startup timeout via LAMBDA_RUNTIME_ENVIRONMENT_TIMEOUTlog patternRead timeout on endpoint URL: "http://localhost:4566/2015-03-31/functions/arn%3Aaws%3Alambda%3Aus-east-1%3A000000000000%3Afunction%3Aproxy-function/invocations"log patternINTEGRATION_FAILUREerror code502http statusTechnical References (13)
Lambda runtime environmentcomponentcold startsconceptprovisioned concurrencyconceptVPC configurationconceptexecution environmentcomponenthot-reloadconceptLOCALSTACK_HOSTNAMEcomponentINITconceptcold startconceptLambda function handlercomponentREPORT statementsconceptREPORT linecomponentInitialization DurationcomponentRelated Insights (7)
Lambda runtime environment startup timeoutwarning
▸
Lambda operations taking 17-30+ seconds due to executor configurationwarning
▸
Lambda latency increases cause pipeline timeouts and slowdownswarning
▸
Lambda execution environment timeout during startup with boto3 and hot-reloadcritical
▸
Lambda cold starts increase IntegrationLatencywarning
▸
Lambda cold starts increase API Gateway integration latencywarning
▸
Lambda cold start increases API Gateway response latencywarning
▸