mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-17 23:52:24 +00:00
fix(heap): report again at 95 % and leave a report on an out-of-memory exit
The pressure report re-armed only after the heap fell under 70 % and half an hour passed, so a heap that climbed to its limit soon after an 85 % report died with only that older report on record. A 95 % tier now writes the same report at once, whatever the cooldown, and re-arms under 85 %. The image sets NODE_OPTIONS so Node writes its diagnostic report to stderr when the heap runs out, with environment variables and network interfaces excluded. The heap-diagnostics and scaling docs say how to keep the flags when overriding NODE_OPTIONS. Heap figures share one megabytes helper with the support report.
This commit is contained in:
1 parent
3cf67d05f9
commit
b79bd8370d
7 files changed
+101
-14
No files matched your search
@@ -76,6 +76,15 @@ ENV NODE_ENV=production
|
||||
ENV NEXT_TELEMETRY_DISABLED=1
|
||||
ENV TZ=Europe/Berlin
|
||||
|
||||
# When the heap runs out, Node writes a diagnostic report (the JavaScript
|
||||
# and native stacks, heap spaces, libuv handles) to stderr, where
|
||||
# `docker compose logs` and Loki keep it; without it the log holds one
|
||||
# line. Environment variables and network interfaces are left out, so no
|
||||
# key, password or address from the environment reaches the log. An
|
||||
# operator who sets NODE_OPTIONS replaces this value and should carry these
|
||||
# flags over (docs/ops/heap-diagnostics.md).
|
||||
ENV NODE_OPTIONS="--report-on-fatalerror --report-filename=stderr --report-exclude-env --report-exclude-network"
|
||||
|
||||
# v1.4.43 B11 — forward NEXT_PUBLIC_APP_VERSION from the builder stage
|
||||
# into the runner so /api/version reads the build-arg value instead of
|
||||
# the package.json fallback. The variable is keyed to the CI tag ref
|
||||
|
||||
Reference in new issue
Block a user