log files

Author: ranbel

src/content/docs/cloudflare-one/connections/connect-networks/troubleshoot-tunnels/diag-logs.mdx

@@ -18,8 +18,7 @@ The steps for getting diagnostic logs depend on your `cloudflared` deployment en
 
 ### Prerequisites
 
-- Access to the `cloudflared` host being diagnosed
-- `cloudflared` version 2024.12.2 or later
+- `cloudflared` version 2024.12.2 or later installed on the host
 
 ### Host environment
 
@@ -134,8 +133,20 @@ This command will output the status of each diagnostic task and place a `cloudfl
 
 ## cloudflared-diag files
 
-The `cloudflared-diag-YYYY-MM-DDTHH-MM-SS.zip` archive contains the files listed below. The data in a file either applies to the `cloudflared` instance being diagnosed (`diagnosee`) or the instance that triggered the diagnosis (`diagnoser`). For example, if your tunnel is running in a Docker container, the diagnosee is the Docker instance and the diagnoser is the host machine instance. The diagnosee and diagnoser could also be the same instance.
+The `cloudflared-diag-YYYY-MM-DDThh-mm-ss.zip` archive contains the files listed below. The data in a file either applies to the `cloudflared` instance being diagnosed (`diagnosee`) or the instance that triggered the diagnosis (`diagnoser`). For example, if your tunnel is running in a Docker container, the diagnosee is the Docker instance and the diagnoser is the host instance.
 
 | File name  | Description | Instance |
 | -| - | - |
-| | | |
+| `cli-configuration.json`| [Tunnel run parameters](/cloudflare-one/connections/connect-networks/configure-tunnels/tunnel-run-parameters/) used when starting the tunnel | diagnosee|
+| `cloudflared_logs.txt` | [Tunnel log file](/cloudflare-one/connections/connect-networks/monitor-tunnels/logs/)[^1]  | diagnosee|
+| `configuration.json` | Tunnel configuration parameters | diagnosee|
+| `goroutine.pprof` | goroutine profile made available by `pprof` | diagnosee|
+| `heap.pprof` | 	heap profile made available by `pprof`| diagnosee|
+| `metrics.txt` | Snapshot of [Tunnel metrics](/cloudflare-one/connections/connect-networks/monitor-tunnels/metrics/#available-metrics) at the time of diagnosis | diagnosee|
+| `network.txt` | JSON traceroutes to Cloudflare's global network using IPv4 and IPv6 | diagnoser|
+| `raw-network.txt` | Raw traceroutes to Cloudflare's global network using IPv4 and IPv6 | diagnoser|
+| `systeminformation.json` | Operating system information and resource usage | diagnosee|
+| `task-result.json` | Result of each diagnostic task | diagnoser |
+| `tunnelstate.json` | Tunnel connections at the time of diagnosis| diagnosee|
+
+[^1]: If the log file is blank, you may need to manually [set the `--loglevel` parameter](/cloudflare-one/connections/connect-networks/monitor-tunnels/logs/#view-logs-on-the-server) when you start the tunnel. This parameter is only required if you ran the tunnel from the CLI using a `cloudflared tunnel run` command. It is not necessary if the tunnel runs as a Linux/macOS service or runs in Docker/Kubernetes.