Reaching out from the Cloudflare team about an upcoming change to how
cloudflared handles logs. We’d like to get your feedback about how you use these logs and how they could be improved. We’re using this page to collect it, but if you’d prefer to reach out directly, please do so.
cloudflared captures logs and provides them in two channels:
- If you invoke
cloudflaredinteractively, from the command-line, the logs are printed in your terminal as a series of time-stamped events.
- If you specify a log file storage location,
cloudflaredwrites logs to that destination (this occurs whether
cloudflaredis run as a service or invoked from the command-line).
We’d like to improve that workflow and have plans to tackle it in two directions:
A simpler UI when invoked interactively
In the first example, those logs become cluttered fast with information that is not entirely useful. We’d like to replace that stream of events with a summary view of your
A default file storage location
Today, we ask you to specify a destination to write logs, which become a log file. We are considering some alternatives about writing those to a more default location like
journald or the Windows event logger.
While we focus on improving those two areas, we’d appreciate your feedback. We have a few short questions - feel free to answer any or all.
- When running
cloudflaredinteractively, what summary information would be valuable to know? This could include the data centers connected, the connection status, or other details.
- When running
cloudflaredinteractively, do you prefer to view the logs as they are streamed?
- Do you have a preferred storage location for writing
cloudflaredlogs beyond specifying a log file location? Would you prefer your operating system log service to a log file on the filesystem?
As always, thank you for your time and for helping make Argo Tunnel better here.