Repository navigation
Send Server application logs to stderr in every deployment path #618
Description
Problem
On Kubernetes, the Server's application logs never reach the container's log stream. They go to a file inside each container, which kubectl logs and cluster log collectors can't see, which is lost on restart, and which grows without rotation.
- The image doesn't set
LOG_CHANNEL(Dockerfile), so Laravel's default applies: thestackchannel writes throughsingletostorage/logs/laravel.log. - Only the published Compose file sets
LOG_CHANNEL: stderr. The Helm chart's ConfigMap and the rawk8s/manifests set no log settings, and this applies to the API, worker and scheduler pods. - The chart's values suggest
DW_LOG_FORMAT: "json", but nothing in the Server reads that variable. - The config reference lists Laravel logging settings but doesn't give the default destination or say how to get JSON output for log pipelines.
Reproduced with the published durableworkflow/server:2.10.1 image. With no LOG_CHANNEL, the resolved channel is stack (single), and an error logged through Laravel appears in storage/logs/laravel.log and not on stderr. With LOG_CHANNEL=stderr it appears on stderr and not in the file.
Acceptance criteria
- Every published deployment path (the image's own default, Compose, the Helm chart and the raw manifests) sends Server application logs to stderr unless the operator chooses otherwise.
- Operators can switch to structured JSON lines through a documented setting, and the chart's example uses a variable the Server actually reads.
- A test or chart check shows an error logged by an API, worker and scheduler process with default chart values reaches the container's stderr.
- The config reference states the default log destination, how to choose JSON output and how to change the level.
Activity
rmcdaniel commentedon Oct 21, 2026
Accepted as a product fix. The implementation will make stderr the image default, carry the same default through chart/raw deployment guidance, honor an operator-selected channel, and document Laravel’s existing LOG_STDERR_FORMATTER for JSON lines. DW_LOG_FORMAT will not be presented as a working setting. Qualification will exercise the real API, worker and scheduler role commands; source, built-image and published acceptance will remain distinct. Work is based on the now-merged image foundation #615, without native, shared-fixture, schema, dependency or frozen-actor changes.
rmcdaniel commentedon Oct 22, 2026
Delivered in published Server 2.11.0 / Helm 0.3.0.
LOG_STDERR_FORMATTER; the unread chart example was corrected.This closes the logging obligation. The separate activity-lease installed-consumer qualification stays on Workflow #878; no Cloud deployment or native release is implied. The optional evidence ZIP download timed out on the Azure delivery path, so no independent ZIP-content audit is claimed. The linked publisher's actual checks and the independently pulled immutable image identities are the evidence here.