localstack.service.operation.duration

AWS service operation duration

Dimensions:None

Available on:

OpenTelemetry (1)

Interface Metrics (1)

OpenTelemetry

localstack.service.operation.duration

Duration of AWS service operation execution

Dimensions:None

Sources

localstack.service.operation.durationdocs.localstack.cloud

Technical Annotations (24)

Configuration Parameters (8)

healthcheck.timeoutrecommended: 10s

Doubled from default 5s to accommodate slower health check responses

healthcheck.start_periodrecommended: 15s

Grace period for container initialization before health checks count toward failure

healthcheck.intervalrecommended: 10s

Time between consecutive health checks

healthcheck.retriesrecommended: 3

Number of consecutive failures before marking container unhealthy

LAMBDA_EXECUTORrecommended: local or docker-reuse

Controls Lambda execution mode; 'local' offers best performance, 'docker-reuse' reuses containers (use local only if no OS-specific C bindings needed)

experimentalrecommended: true

Required in Docker daemon.json when using Windows container mode with Linux containers

Statisticrecommended: Average

Statistical method for evaluating latency metric

Periodrecommended: 5 minutes

Evaluation period for latency measurements

Error Signatures (2)

Health check exceeded timeout (5s)log pattern

-1exit code

CLI Commands (4)

.venv/bin/localstack status services --format=jsondiagnostic

docker exec localstack_linux python3 -c "print('\n127.0.0.1 localhost\n', file=open('/etc/hosts', 'a'))"remediation

docker run --network linux-dependencies --platform linux --name localstack_linux -d -p 4566:4566 -e SERVICES=sqs,sns,logs -e EAGER_SERVICE_LOADING=1 localstack/localstack:0.13.2

diagnostic

mountdiagnostic

Technical References (10)

docker-compose healthcheckconceptservice_healthy conditioncomponentdynamodb-localcomponentdynalitecomponentdocker-composecomponent/etc/hostsfile pathWindows container modecomponentDocker Desktop for WindowscomponentWSL2componentDebian base imagecomponent

Related Insights (6)

LocalStack health check timeout causes false unhealthy statuswarning

▸

DynamoDB Local performance degrades 6-10x when running inside LocalStackwarning

▸

Lambda operations taking 17-30+ seconds due to executor configurationwarning

▸

Insufficient Docker resources cause LocalStack performance degradationwarning

▸

Missing /etc/hosts causes 10x SQS performance degradation in Windows container modewarning

▸

Microservice API latency exceeds SLA thresholdscritical

▸