localstack.http.server.active_requests

Active HTTP requests

Dimensions:None

Available on:

OpenTelemetry (1)

Interface Metrics (1)

OpenTelemetry

localstack.http.server.active_requests

Number of active HTTP requests currently being processed

Dimensions:None

Sources

localstack.http.server.active_requestsdocs.localstack.cloud

Technical Annotations (19)

Configuration Parameters (2)

S3_HOSTNAMErecommended: localstack:4566

Default s3.localhost.localstack.cloud fails in container-to-container networking; use service name instead

AWS_ENDPOINT_URLrecommended: http://localstack:4566

LocalStack API endpoint for container-to-container communication

Error Signatures (4)

Listening at http://:::51679log pattern

dial tcp: lookup s3.localhost.localstack.cloud: no such hostlog pattern

dial tcp 127.0.0.1:4566: connect: connection refusedlog pattern

RequestError: send request failedlog pattern

CLI Commands (5)

docker exec -it ls /bin/bashdiagnostic

while true; do time curl localhost:4566; sleep 0.1; donediagnostic

docker compose -f docker-compose.dev.yaml run --rm --entrypoint curl local_terraform_setup http://localstack:4566/_localstack/health

diagnostic

docker compose -f docker-compose.dev.yaml run --rm --entrypoint rm local_terraform_setup -f localstack_providers_override.tf

remediation

docker compose -f docker-compose.dev.yaml run --rm --entrypoint tflocal local_terraform_setup apply -auto-approveremediation

Technical References (8)

docker-compose.ymlfile pathport 51679componentport 4566componentconnection poolconcepttflocalcomponentProvider Overrideconceptlocalstack_providers_override.tffile pathDocker Compose networkcomponent

Related Insights (3)

LocalStack stops responding after showing listening message on port 51679critical

▸

TCP connection pooling causes linear request latency degradationwarning

▸

Terraform apply fails with connection refused when LocalStack runs in separate Docker containercritical

▸