Closed itodor closed 1 week ago
This is totally expected (and a common practice for cloud native apps). Logs are diagnose information traditionally outputted on stderr.
We'll stick to Caddy defaults, however Caddy and so Mercure provide configuration to customize this and that may allow you to achieve what you want: https://caddyserver.com/docs/caddyfile/directives/log
I'm noticing that all logs, including normal, successful request logs with 200 status, are outputted to stderr by default, even though these logs do not indicate any errors.
To verify this, I ran a clean local instance of Mercure with the following command:
When I accessed the Mercure UI in my browser and repeatedly clicked the “Subscribe to topic” button, I observed that stderr.txt was filling up with logs, while stdout.txt remained empty. This behavior suggests that all request logs, even for successful 200 responses, are being directed to stderr.
Could you confirm if this is the expected behavior, or if there’s a configuration option I might be missing to correctly separate normal request logs (to stdout) from actual error logs (to stderr)?
Thank you for your help in understanding this behavior.
Example of logs when I click 'subscribe to topic':