How can I configure Erlang's error_logger to persist logs to a file for post‑mortem analysis of a failed deployment?
When an Erlang release fails during deployment, the default error_logger output goes to the console and can be lost if the node terminates abruptly. To diagnose the failure later, I need to capture error_logger events in a file that survives node crashes and is available for offline inspection. Using error_logger:logfile/1 redirects logs to a file, but I am
erlang