Streamlit upload limit logs omit configured maxUploadSize value

Diagnosing upload limit failures from Streamlit logs

The goal is to ascertain, solely from the server’s stderr output, whether a rejected file upload was caused by exceeding the server.maxUploadSize setting.

Currently, when a file surpasses the limit, Streamlit logs the actual uploaded size but omits the configured limit, and no stack trace is emitted unless the logger is set to DEBUG. This makes it impossible to distinguish a limit‑related failure from other upload errors without inspecting the configuration file or restarting the service with altered logging.

Is it possible to configure Streamlit to include the server.maxUploadSize value in the error message? Can enabling DEBUG level reliably provide a traceback that reveals the limit check? Should operators rely on external metrics or configuration‑change events instead of log‑only diagnosis?