update existing logs page

Author: ranbel

src/content/docs/cloudflare-one/connections/connect-networks/configure-tunnels/tunnel-run-parameters.mdx

@@ -22,7 +22,7 @@ By default, `cloudflared` will periodically check for updates and restart with t
 
 :::note
 
-For locally-managed tunnels only. 
+For locally-managed tunnels only.
 :::
 
 | Syntax                                                  | Default                     |
@@ -75,7 +75,7 @@ Saves application log to this file. Mainly useful for reporting issues. For more
 | ---------------------------------------------------------- | ------- | -------------------- |
 | `cloudflared tunnel --loglevel <VALUE> run <UUID or NAME>` | `info`  | `TUNNEL_LOGLEVEL`    |
 
-Specifies the verbosity of logging. The default `info` level does not produce much output, but you may wish to use the `warn` level in production. Available values are: `debug`, `info`, `warn`, `error`, `fatal`.
+Specifies the verbosity of logging for the local `cloudflared` instance. Available values are `debug`, `info` (default), `warn`, `error`, and `fatal`. At the `debug` level, `cloudflared` will log and display the request URL, method, protocol, content length, as well as all request and response headers. However, note that this can expose sensitive information in your logs.
 
 ## `metrics`
 
@@ -97,7 +97,7 @@ Disables automatic `cloudflared` updates. See also: [`autoupdate-freq`](#autoupd
 
 :::note
 
-For locally-managed tunnels only. 
+For locally-managed tunnels only.
 :::
 
 | Syntax                                                      | Default                   | Environment Variable |
@@ -152,7 +152,7 @@ Specifies custom tags used to identify this tunnel. Multiple tags may be specifi
 
 :::note
 
-For remotely-managed tunnels only. 
+For remotely-managed tunnels only.
 :::
 
 | Syntax                                          | Environment Variable |

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

@@ -1,58 +1,42 @@
 ---
 pcx_content_type: reference
-title: Logs
+title: Log streaming
 sidebar:
   order: 1
 head:
   - tag: title
-    content: Tunnel logs
+    content: Tunnel log streams
 ---
 
 Tunnel logs record all activity between a `cloudflared` instance and Cloudflare's global network, as well as all activity between `cloudflared` and your origin server. These logs allow you to investigate connectivity or performance issues with a Cloudflare Tunnel. You can configure your server to store persistent logs, or you can stream real-time logs from any client machine.
 
 ## View logs on the server
 
-If you have access to the origin server, you can enable logging when you start the tunnel:
+If you have access to the origin server, you can use the [`--loglevel` flag](/cloudflare-one/connections/connect-networks/configure-tunnels/tunnel-run-parameters/#loglevel) to enable logging when you start the tunnel. By default, `cloudflared` prints logs to stdout and does not store logs on the server. You can optionally use the [`--logfile` flag](/cloudflare-one/connections/connect-networks/configure-tunnels/tunnel-run-parameters/#logfile) to write your logs to a file.
 
-```sh
-cloudflared tunnel --loglevel debug run <UUID>
-```
-
-The [`--loglevel` flag](/cloudflare-one/connections/connect-networks/configure-tunnels/tunnel-run-parameters/#loglevel) indicates the logging level for the local `cloudflared` instance, which can be one of {`debug`, `info`, `warn`, `error`, `fatal`} (default: `info`). At the `debug` level, `cloudflared` will log and display the request URL, method, protocol, content length, as well as all request and response headers. However, note that this can expose sensitive information in your logs.
-
-### Write logs to file
-
-By default, `cloudflared` prints logs to stdout and does not store logs on the server. You can use the [`--logfile` flag](/cloudflare-one/connections/connect-networks/configure-tunnels/tunnel-run-parameters/#logfile) to save your logs to a file:
+To enable logs for a locally-managed tunnel:
 
 ```sh
-cloudflared tunnel --logfile mytunnel.log run <UUID>
+cloudflared tunnel --loglevel debug --logfile cloudflared.log run <UUID>
 ```
 
+To enable logs for a remotely-managed tunnel, add `--loglevel debug` and `--logfile <PATH>` to your system service as shown in [Add tunnel run parameters](/cloudflare-one/connections/connect-networks/configure-tunnels/remote-management/#add-tunnel-run-parameters).
+
 ## View logs on your local machine
 
-You can view real-time logs for a Cloudflare Tunnel via the dashboard or from any machine that has `cloudflared` installed. With remote log streams, you do not need to SSH into the server that is running the tunnel.
+You can view real-time logs for a Cloudflare Tunnel via the dashboard or from any machine that has `cloudflared` installed. With remote log streams, you do not need to SSH into the server that is running the tunnel. To get remote logs, the tunnel must be active and able to receive requests.
 
 ### Dashboard
 
-#### Prerequisites
+Dashboard log streams are only available for remotely-managed tunnels. To view logs from the dashboard:
 
-- `cloudflared` version 2023.5.1 or higher is installed on the origin server.
-- The tunnel is active and able to receive requests.
-
-#### View logs
-
-1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Networks** > **Tunnels** and select your tunnel.
+1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Networks** > **Tunnels** and select a remotely-managed tunnel.
 2. In the sidebar, select the **Connector ID** for the `cloudflared` instance you want to view.
 3. Select **Begin log stream**.
 
 ### CLI
 
-The `cloudflared` daemon can stream logs from any tunnel in your account to the local command line.
-
-#### Prerequisites
-
-- `cloudflared` version 2023.5.1 or higher is installed on both your local machine and the origin server.
-- The tunnel is active and able to receive requests.
+The `cloudflared` daemon can stream logs from any tunnel in your account to the local command line. `cloudflared` must be installed on both your local machine and the origin server.
 
 #### View logs