Skip to content

fix(compose): map the EVENT_LOOP_MONITOR_* knobs into the api service (#3236) #3238

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.

Sign up for GitHub

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

Merged
ToddHebebrand merged 2 commits into from
Aug 8, 2026
Merged

fix(compose): map the EVENT_LOOP_MONITOR_* knobs into the api service (#3236) #3238

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
34b50a3
fix(compose): map the EVENT_LOOP_MONITOR_* knobs into the api service…
bdunncompany Aug 8, 2026
9cdc514
Merge branch 'main' into fix/3236-event-loop-monitor-compose
ToddHebebrand Aug 8, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions deploy/docker-compose.prod.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -100,6 +100,16 @@ services:
DB_POOL_HEALTH_MIN_TIMEOUTS: ${DB_POOL_HEALTH_MIN_TIMEOUTS:-}
DB_POOL_HEALTH_PROBE_TIMEOUT_MS: ${DB_POOL_HEALTH_PROBE_TIMEOUT_MS:-}
DB_POOL_HEALTH_CAPTURE_THROTTLE_MS: ${DB_POOL_HEALTH_CAPTURE_THROTTLE_MS:-}
# Event-loop lag monitor (#3024). Same reasoning as the pool-health block
# above: deploy/environment.mdx documents these as working knobs, and an
# unmapped var set in .env is silently inert. The monitor runs on its
# defaults either way, so this only ever blocked tuning — but an operator
# raising the warn threshold to cut noise, or setting DISABLED to turn it
# off, saw no change and no error. All optional: an empty value reads as
# unset and the code applies its own defaults.
EVENT_LOOP_MONITOR_INTERVAL_MS: ${EVENT_LOOP_MONITOR_INTERVAL_MS:-}
EVENT_LOOP_STARVATION_WARN_MS: ${EVENT_LOOP_STARVATION_WARN_MS:-}
EVENT_LOOP_MONITOR_DISABLED: ${EVENT_LOOP_MONITOR_DISABLED:-}
REDIS_HOST: redis
REDIS_PORT: 6379
REDIS_PASSWORD_FILE: /run/secrets/redis_password
Expand Down
10 changes: 10 additions & 0 deletions docker-compose.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -102,6 +102,16 @@ services:
DB_POOL_HEALTH_MIN_TIMEOUTS: ${DB_POOL_HEALTH_MIN_TIMEOUTS:-}
DB_POOL_HEALTH_PROBE_TIMEOUT_MS: ${DB_POOL_HEALTH_PROBE_TIMEOUT_MS:-}
DB_POOL_HEALTH_CAPTURE_THROTTLE_MS: ${DB_POOL_HEALTH_CAPTURE_THROTTLE_MS:-}
# Event-loop lag monitor (#3024). Same reasoning as the pool-health block
# above: deploy/environment.mdx documents these as working knobs, and an
# unmapped var set in .env is silently inert. The monitor runs on its
# defaults either way, so this only ever blocked tuning — but an operator
# raising the warn threshold to cut noise, or setting DISABLED to turn it
# off, saw no change and no error. All optional: an empty value reads as
# unset and the code applies its own defaults.
EVENT_LOOP_MONITOR_INTERVAL_MS: ${EVENT_LOOP_MONITOR_INTERVAL_MS:-}
EVENT_LOOP_STARVATION_WARN_MS: ${EVENT_LOOP_STARVATION_WARN_MS:-}
EVENT_LOOP_MONITOR_DISABLED: ${EVENT_LOOP_MONITOR_DISABLED:-}
REDIS_HOST: redis
REDIS_PORT: 6379
REDIS_PASSWORD_FILE: /run/secrets/redis_password
Expand Down
Loading