Skip to content

Commit b2eb146

Browse files
[CF1] linux log note (#25586)
1 parent accd547 commit b2eb146

File tree

1 file changed

+11
-1
lines changed
  • src/content/docs/cloudflare-one/connections/connect-devices/warp/troubleshooting

1 file changed

+11
-1
lines changed

src/content/docs/cloudflare-one/connections/connect-devices/warp/troubleshooting/warp-logs.mdx

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -138,7 +138,7 @@ The `warp-debugging-info` folder may contain multiple versions of the same log,
138138
In timestamped logs such as `daemon.log`, the most recent events will appear at the end of the file.
139139
:::
140140

141-
#### Log retention window
141+
### Log retention window
142142

143143
Each WARP log file (such as `connection_stats.log`, `dns_stats.log`, `daemon.log`, `boringtun.log`, `daemon_dns.log`, `dex.log` and `captive-portal.log`) is limited by size and age:
144144

@@ -150,6 +150,16 @@ Log files may include data from up to 96 hours (four days) prior to when `warp-d
150150

151151
Always check the timestamps at the end of each log file to verify the time range covered by the diagnostic archive.
152152

153+
:::note[Linux log behavior]
154+
155+
On Linux, the WARP daemon logs are written to the system logs by the `warp-svc` service.
156+
157+
If you need to adjust the maximum log level or filter what gets logged, you can configure the WARP `systemd` unit file using the [`LogLevelMax=` option](https://www.freedesktop.org/software/systemd/man/latest/systemd.exec.html#LogLevelMax=).
158+
159+
Cloudflare WARP does not provide an official method to configure logging levels during the installation process.
160+
161+
:::
162+
153163
## iOS/Android/ChromeOS
154164

155165
### Collect logs

0 commit comments

Comments
 (0)