Add docs for "remote timestamps" enhancement

src/pages/docs/tasks/index.md

@@ -1,7 +1,7 @@
 ---
 layout: src/layouts/Default.astro
 pubDate: 2023-10-20
-modDate: 2024-05-24
+modDate: 2026-09-17
 title: Tasks
 subtitle: The task view shows waiting, running, and completed tasks
 icon: fa-solid fa-list-check
@@ -12,3 +12,5 @@ navOrder: 100
 ---
 
 Many of the main operations Octopus performs are represented by Tasks. This includes all deployments and runbook runs, and system operations such as applying retention policies. Since Tasks consume resources on the Octopus Server while they are executing, the number of Tasks which can execute at the same time is limited by a task cap. See [increasing the task cap](/docs/support/increase-the-octopus-server-task-cap) for more information.
+
+Each task has a task log recording what happened while it ran. Every log line carries both the time Octopus Server observed the output and the time the machine that produced it says it occurred. See [task log timestamps](/docs/tasks/task-log-timestamps) for how to switch between the two.

src/pages/docs/tasks/task-log-timestamps.md

@@ -0,0 +1,42 @@
+---
+layout: src/layouts/Default.astro
+pubDate: 2026-09-17
+modDate: 2026-09-17
+title: Task Log Timestamps
+description: Task log lines record both the time Octopus Server observed the output and the time the machine that produced it says it occurred.
+---
+
+:::div{.info}
+Remote timestamps are available from version `2026.4.3241`.
+:::
+
+Every line in a task log is stamped with two times:
+
+- **Server** (or "Observed") is when Octopus Server observed the output. Octopus has always recorded this time, the task log is always ordered by it, and it's what you see by default.
+- **Remote** (or "Occurred") is when the deployment target or worker that produced the output says it occurred, according to the remote machine's clock.
+
+## Choose which timestamps to show
+
+1. Open the deployment, runbook run, or other task, and select the **Task Log** tab.
+2. Open the view settings menu.
+3. Under **Timestamps**, choose **Hide**, **Server**, or **Remote**.
+
+![Remote timestamps options with remote selected and highlighted in the task log](/docs/img/tasks/images/remote-timestamp.png)
+
+In **Remote** mode, lines that carry a time reported by a target are marked **Remote**. The rest fall back to the server time, because that's the only time Octopus has for them. Hover over any timestamp to see the other time for that line.
+
+:::div{.hint}
+Remote times come from the clock on another machine, so a target with a clock that's out of step with your Octopus Server will report times that look wrong.
+:::
+
+## Why the two times differ
+
+Output from a remote machine doesn't reach Octopus Server the instant a script writes it. A polling Tentacle only sends output when it next checks in, a slow network adds delay on the server-time of remote output.
+
+## Downloading the raw log
+
+The raw task log uses server timestamps by default. To get remote timestamps instead, add the `timestamps` query parameter to the [raw task log endpoint](/docs/api/tasks).
+
+> `GET /api/{spaceId}/tasks/{id}/raw?timestamps=Remote`
+
+Valid values are `Server` (default) and `Remote`.