Repository: seqeralabs/docs
Pull request #581: [PLAT-2252] Document run details page enhancements
Author: login: llewellyn-sl
Labels: name: 2. Reviews complete
description: Reviews complete. Remove label when confirmed in prod.
Created: 2025-05-02T18:58:17Z | Merged: 2025-05-14T18:52:49Z

@netlify platform-cloud/monitoring/run-details

Preview on https://deploy-preview-581--seqera-docs.netlify.app/platform-cloud/monitoring/run-details


Diff:
diff --git a/platform-cloud/docs/monitoring/_images/command.png b/platform-cloud/docs/monitoring/_images/command.png
new file mode 100644
index 000000000..5e2016510
Binary files /dev/null and b/platform-cloud/docs/monitoring/_images/command.png differ
diff --git a/platform-cloud/docs/monitoring/_images/configuration.png b/platform-cloud/docs/monitoring/_images/configuration.png
new file mode 100644
index 000000000..6efd53594
Binary files /dev/null and b/platform-cloud/docs/monitoring/_images/configuration.png differ
diff --git a/platform-cloud/docs/monitoring/_images/containers.png b/platform-cloud/docs/monitoring/_images/containers.png
new file mode 100644
index 000000000..6b56f3042
Binary files /dev/null and b/platform-cloud/docs/monitoring/_images/containers.png differ
diff --git a/platform-cloud/docs/monitoring/_images/datasets.png b/platform-cloud/docs/monitoring/_images/datasets.png
new file mode 100644
index 000000000..994fa31b2
Binary files /dev/null and b/platform-cloud/docs/monitoring/_images/datasets.png differ
diff --git a/platform-cloud/docs/monitoring/_images/executor-details.png b/platform-cloud/docs/monitoring/_images/executor-details.png
new file mode 100644
index 000000000..0fa0322a5
Binary files /dev/null and b/platform-cloud/docs/monitoring/_images/executor-details.png differ
diff --git a/platform-cloud/docs/monitoring/_images/infra-details.png b/platform-cloud/docs/monitoring/_images/infra-details.png
new file mode 100644
index 000000000..15331fc9b
Binary files /dev/null and b/platform-cloud/docs/monitoring/_images/infra-details.png differ
diff --git a/platform-cloud/docs/monitoring/_images/interactive-plot.png b/platform-cloud/docs/monitoring/_images/interactive-plot.png
new file mode 100644
index 000000000..14b7bc17c
Binary files /dev/null and b/platform-cloud/docs/monitoring/_images/interactive-plot.png differ
diff --git a/platform-cloud/docs/monitoring/_images/load.png b/platform-cloud/docs/monitoring/_images/load.png
new file mode 100644
index 000000000..32d358a01
Binary files /dev/null and b/platform-cloud/docs/monitoring/_images/load.png differ
diff --git a/platform-cloud/docs/monitoring/_images/metrics-tiles.png b/platform-cloud/docs/monitoring/_images/metrics-tiles.png
new file mode 100644
index 000000000..81562c355
Binary files /dev/null and b/platform-cloud/docs/monitoring/_images/metrics-tiles.png differ
diff --git a/platform-cloud/docs/monitoring/_images/parameters.png b/platform-cloud/docs/monitoring/_images/parameters.png
new file mode 100644
index 000000000..75baf3791
Binary files /dev/null and b/platform-cloud/docs/monitoring/_images/parameters.png differ
diff --git a/platform-cloud/docs/monitoring/_images/progress-bar.png b/platform-cloud/docs/monitoring/_images/progress-bar.png
new file mode 100644
index 000000000..c3ff13f49
Binary files /dev/null and b/platform-cloud/docs/monitoring/_images/progress-bar.png differ
diff --git a/platform-cloud/docs/monitoring/_images/reports.png b/platform-cloud/docs/monitoring/_images/reports.png
new file mode 100644
index 000000000..98b73ee48
Binary files /dev/null and b/platform-cloud/docs/monitoring/_images/reports.png differ
diff --git a/platform-cloud/docs/monitoring/_images/run-details.png b/platform-cloud/docs/monitoring/_images/run-details.png
new file mode 100644
index 000000000..0836a9af1
Binary files /dev/null and b/platform-cloud/docs/monitoring/_images/run-details.png differ
diff --git a/platform-cloud/docs/monitoring/_images/task-details.png b/platform-cloud/docs/monitoring/_images/task-details.png
new file mode 100644
index 000000000..15667335a
Binary files /dev/null and b/platform-cloud/docs/monitoring/_images/task-details.png differ
diff --git a/platform-cloud/docs/monitoring/_images/task-status-tiles.png b/platform-cloud/docs/monitoring/_images/task-status-tiles.png
new file mode 100644
index 000000000..047151c2d
Binary files /dev/null and b/platform-cloud/docs/monitoring/_images/task-status-tiles.png differ
diff --git a/platform-cloud/docs/monitoring/_images/utilization.png b/platform-cloud/docs/monitoring/_images/utilization.png
new file mode 100644
index 000000000..1a970d4ea
Binary files /dev/null and b/platform-cloud/docs/monitoring/_images/utilization.png differ
diff --git a/platform-cloud/docs/monitoring/run-details.md b/platform-cloud/docs/monitoring/run-details.md
deleted file mode 100644
index 3d547a564..000000000
--- a/platform-cloud/docs/monitoring/run-details.md
+++ /dev/null
@@ -1,167 +0,0 @@
----
-title: "Run details"
-description: "Monitoring a Nextflow pipeline executed through Seqera Platform."
-date: "21 Apr 2023"
-tags: [logging, monitoring, execution]
----
-
-Select a workflow run from the **Runs** list to view execution details. This view contains:
-
-- [Run information](#run-information) with real-time Nextflow execution details
-- [General summary](#general-summary) and [task status](#task-status)
-- List of pipeline [processes](#processes)
-- [Aggregated stats](#aggregate-stats), [load](#load), and [utilization](#utilization)
-- [Tasks](#tasks) and [metrics](#metrics)
-
-### Run information
-
-This section contains details about the Nextflow execution:
-
-- The Nextflow **Command line** executed.
-- The pipeline **Parameters** (taken from the configuration `params` scope).
-- The **Configuration** files and the final resolved configuration.
-- The **Execution log** from the main Nextflow process, updated in real-time.
-- Available **Reports**, if any are [configured](../reports/overview).
-
-### General summary
-
-The **General** panel displays top-level information about a pipeline run:
-
-- Unique workflow run ID
-- Run name
-- Timestamp of run start
-- Project revision and Git commit ID
-- Nextflow session ID
-- Username of the launcher
-- Work directory path
-
-  :::tip
-  If your work directory resides in cloud storage, select the work directory path in the **General** panel to browse its contents in [Data Explorer](../data/data-explorer).
-  :::
-
-- Container image
-- Executor
-- Compute environment name
-- Resource labels
-- Nextflow version
-
-Hover over each item with the cursor to view a description. Hover over the compute environment name for more compute environment details.
-
-### Task status
-
-The **Status** panel provides a real-time status of all tasks in the pipeline run:
-
-- **pending**: The task has been created, but not yet submitted to an executor
-- **submitted**: The task has been submitted to an executor, but is not yet running
-- **running**: The task has been launched by an executor (the precise definition of "running" may vary for each executor)
-- **cached**: A previous (and valid) execution of the task was found and used instead of executing the task again (See [Cache and resume](../launch/cache-resume))
-- **completed**: The task completed successfully
-- **failed**: The task failed
-
-### Processes 
-
-The **Processes** panel displays the status of each process in a pipeline run. In Nextflow, a process is an individual step in a pipeline, while a task is a particular invocation of a process for given input data. In the panel, each process is shown with a progress bar indicating how many tasks have been completed for that process.
-
-The progress bar is color-coded based on task status (**created**, **submitted**, **completed**, **failed**).
-
-Select a process to navigate to the [Tasks](#tasks) panel and filter the table contents by the selected process.
-
-### Aggregate stats 
-
-The **Aggregate stats** panel displays a real-time summary of the resources used by a pipeline run.
-
-#### Wall time
-
-The _wall time_ is the duration of the entire workflow run, from submission to completion.
-
-#### CPU time
-
-The _CPU time_ is the total CPU time used by all tasks. It is based on the CPUs _requested_, not the actual CPU usage. The CPU time of an individual task is computed as follows:
-
-$$
-\text{CPU time (CPU-hours)} = \text{Task CPUs} \times \text{Task runtime}
-$$
-
-The runtime of an individual task is computed as follows:
-
-$$
-\text{Task runtime} = \text{Task complete} - \text{Task start}
-$$
-
-See also: **cpus**, **start**, and **complete** in the task table.
-
-#### Total memory
-
-The _total memory_ is the total memory used by all tasks. It is based on the memory _requested_, not the actual memory usage.
-
-See also: **peakRss** in the task table.
-
-#### Read and write
-
-The _read_ and _write_ are the total amount of data read from and written to storage.
-
-See also: **readBytes** and **writeBytes** in the task table.
-
-#### Estimated cost
-
-See [Cloud costs](../monitoring/cloud-costs#seqera-cost-estimate). 
-
-### Load
-
-The **Load** panel displays the current number of running tasks and CPU cores vs the maximum number of tasks and CPU cores for the entire pipeline run.
-
-These metrics measure the level of parallelism achieved by the pipeline. Use these metrics to determine whether your pipeline runs are fully utilizing the capacity of your compute environment.
-
-### Utilization
-
-The **Utilization** panel displays the average resource utilization of all tasks that have completed successfully in a pipeline run. The CPU and memory efficiency of a task are computed as follows:
-
-$$
-\text{CPU efficiency (\%)} = \text{CPU usage (\%)} \times \text{Task CPUs}
-$$
-
-$$
-\text{Memory efficiency (\%)} = \frac{ \text{Peak memory usage} }{ \text{Task memory} } \times \text{100 \%}
-$$
-
-See also: **pcpu**, **cpus**, **peakRss**, and **memory** in the task table.
-
-These metrics measure how efficiently the pipeline is using its compute resources. Low utilization indicates that the pipeline may be over-requesting resources for some tasks.
-
-### Tasks 
-
-The **Tasks** panel shows all the tasks that were executed in a pipeline run.
-
-#### Search and filter tasks
-
-Use the search bar to filter tasks with substrings in the table columns such as **process**, **tag**, **hash**, and **status**. For example, if you enter `succeeded` in the **Search task** field, the table displays only tasks that succeeded.
-
-#### Task details
-
-Select a task in the task table to open the **Task details** dialog. The dialog has three tabs:
-
-- **About**
-  - **Name**: Process name and tag
-  - **Command**: Task script, defined in the pipeline process
-  - **Status**: Exit code, task status, attempts
-  - **Work directory**: Directory where the task was executed
-  - **Environment**: Environment variables supplied to the task
-  - **Execution time**: Metrics for task submission, start, and completion time
-  - **Resources requested**: Metrics for the resources requested by the task
-  - **Resources used**: Metrics for the resources used by the task
-
-- **Execution log**
-
-  The **Execution log** tab provides a real-time log of the selected task's execution. Task execution and other logs (such as `stdout` and `stderr`) are available for download from here, if still available in your compute environment.
-
-- **Data Explorer**
-
-  If the pipeline work directory is in cloud storage, this tab shows a [Data Explorer](../data/data-explorer) view of the task's work directory location with the files associated with the task.
-
-### Metrics 
-
-The **Metrics** panel displays interactive plots for CPU usage, memory usage, task duration, and I/O usage, grouped by process. These metrics include succeeded and failed tasks. Use these plots to quickly inspect a pipeline run to determine the resources requested and consumed by each process.
-
-:::tip
-Hover the cursor over each box plot to show more details.
-:::
\ No newline at end of file
diff --git a/platform-cloud/docs/monitoring/run-details.mdx b/platform-cloud/docs/monitoring/run-details.mdx
new file mode 100644
index 000000000..2b4a8908e
--- /dev/null
+++ b/platform-cloud/docs/monitoring/run-details.mdx
@@ -0,0 +1,266 @@
+---
+title: "Run details"
+description: "Monitoring a Nextflow pipeline executed through Seqera Platform."
+date: "21 Apr 2023"
+tags: [logging, monitoring, execution]
+---
+
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
+Select a workflow run from the **Runs** list to open a run details page. 
+
+![Run details and progress overview](./_images/progress-bar.png)
+
+The top of the page contains basic run details and a progress overview for an at-a-glance view of the run's status:
+- View and copy the run ID, pipeline name and repository, pipeline work directory, compute environment, and launch date. 
+- Select the star icon to favorite the run and find it more easily via a filter view in the runs list later. 
+- Use the options menu to apply labels, relaunch, resume, or delete the run, or to save the run as a new pipeline. 
+
+Select the tabs below the workflow run progress bar to view further run details:
+- **Tasks**: View the status and progress of pipeline tasks and [processes](#processes), including extensive [task details](#tasks)
+- **Logs**: View and download the pipeline run's execution logs
+- **Metrics**: View resource [metrics](#wall-time) for the run 
+- **Configuration**: View Nextflow configuration files and the resolved [configuration](#configuration) used for the run
+- **Datasets**: View [datasets](../data/datasets) used as input for the run, if any
+- **Reports**: View [reports](../reports/overview) for the run, if any were configured
+- **Containers**: View the details of containers used in the run, if any
+- **Run Info**: View details about the [run](#run-details), [infrastructure](#infrastructure-details), and [executor](#executors-details)
+
+<Tabs>
+<TabItem value="Tasks" label="Tasks" default>
+
+![Task status overview](./_images/task-status-tiles.png)
+
+The cards at the top of the **Tasks** tab provide a real-time status of all tasks in the pipeline run:
+
+- **Pending**: The task has been created, but not yet submitted to an executor
+- **Submitted**: The task has been submitted to an executor, but is not yet running
+- **Running**: The task has been launched by an executor (the precise definition of "running" may vary for each executor)
+- **Cached**: A previous (and valid) execution of the task was found and used instead of executing the task again. See [Cache and resume](../launch/cache-resume.mdx)
+- **Succeeded**: The task completed successfully
+- **Failed**: The task failed
+- **Aborted**: The task was submitted, but the run was cancelled or failed before the task could begin
+
+### Processes 
+
+The **Processes** panel displays the status of each process in a pipeline run. In Nextflow, a process is an individual step in a pipeline, while a task is a particular invocation of a process for given input data. In the panel, each process is shown with a progress bar indicating how many tasks have been completed for that process.
+
+The progress bar is color-coded based on task status (**created**, **submitted**, **completed**, **failed**).
+
+Select a process to navigate to the [Tasks](#tasks) panel and filter the table contents by the selected process.
+
+### Tasks 
+
+The **Tasks** panel shows all the tasks that were executed in the run.
+
+Use the search bar to filter tasks with substrings in the table columns such as **process**, **tag**, **hash**, and **status**. For example, if you enter `succeeded` in the **Search task** field, the table displays only tasks that succeeded.
+
+#### Task details
+
+![Task details](./_images/task-details.png)
+
+Select a task in the task table to open the **Task details** dialog. The dialog has three tabs:
+
+- **About**
+  - **Name**: Process name and tag
+  - **Command**: Task script, defined in the pipeline process
+  - **Status**: Exit code, task status, attempts
+  - **Work directory**: Directory where the task was executed
+  - **Environment**: Environment variables supplied to the task
+  - **Execution time**: Metrics for task submission, start, and completion time
+  - **Resources requested**: Metrics for the resources requested by the task
+  - **Resources used**: Metrics for the resources used by the task
+
+- **Execution log**
+
+  The **Execution log** tab provides a real-time log of the selected task's execution. Task execution and other logs (such as `stdout` and `stderr`) are available for download if they are still available in your compute environment.
+
+- **Data Explorer**
+
+  If the pipeline work directory is in cloud storage, this tab shows a [Data Explorer](../data/data-explorer) view of the task's work directory location with the files associated with the task.
+
+</TabItem>
+<TabItem value="Logs" label="Logs" default>
+
+The **Logs** tab contains a window with the Nextflow execution log console output. Select **Download log files** to download: 
+- Nextflow console output, in TXT format.
+- Nextflow log file, in LOG format.
+- Execution timeline graph, in HTML format.
+
+</TabItem>
+<TabItem value="Metrics" label="Metrics" default>
+
+The cards at the top of the **Metrics** tab display a real-time summary of the resources used by the run.
+
+![Metrics overview](./_images/metrics-tiles.png)
+
+#### Wall time
+
+Wall time is the duration of the entire workflow run, from submission to completion. While the run is in progress, wall time is a measure of the time elapsed since run start. 
+
+#### CPU time
+
+CPU time is the total CPU time used by all tasks, measured in CPU hours. It is based on the CPUs _requested_, not the actual CPU usage. The CPU time of an individual task is computed as follows:
+
+$$
+\text{CPU time (CPU-hours)} = \text{Task CPUs} \times \text{Task runtime}
+$$
+
+The runtime of an individual task is computed as follows:
+
+$$
+\text{Task runtime} = \text{Task complete} - \text{Task start}
+$$
+
+See also: **cpus**, **start**, and **complete** in the task table.
+
+#### Memory
+
+Memory is the total memory used by all tasks. It is based on the memory _requested_, not the actual memory usage.
+
+See also: **peakRss** in the task table.
+
+#### Data read and write
+
+Data read and Data write are the total amount of data (in GB) read from and written to storage.
+
+See also: **readBytes** and **writeBytes** in the task table.
+
+#### Estimated cost
+
+An estimated cost for the run. See [Seqera cost estimate](../monitoring/cloud-costs#seqera-cost-estimate) for details. 
+
+#### Load
+
+![Load](./_images/load.png)
+
+The **Load** panel displays the current number of running tasks and CPU cores vs the maximum number of tasks and CPU cores for the entire pipeline run.
+
+These metrics measure the level of parallelism achieved by the pipeline. Use these metrics to determine whether your pipeline runs are fully utilizing the capacity of your compute environment.
+
+#### Utilization
+
+![Utilization](./_images/utilization.png)
+
+The **Utilization** panel displays the average resource utilization of all tasks that have completed successfully in a pipeline run. The CPU and memory efficiency of a task are computed as follows:
+
+$$
+\text{CPU efficiency (\%)} = \text{CPU usage (\%)} \times \text{Task CPUs}
+$$
+
+$$
+\text{Memory efficiency (\%)} = \frac{ \text{Peak memory usage} }{ \text{Task memory} } \times \text{100 \%}
+$$
+
+See also: **pcpu**, **cpus**, **peakRss**, and **memory** in the task table.
+
+These metrics measure how efficiently the pipeline is using its compute resources. Low utilization indicates that the pipeline may be over-requesting resources for some tasks.
+
+#### Interactive resource plots
+
+![Interactive CPU plot](./_images/interactive-plot.png)
+
+The **CPU**, **Memory**, **Job duration**, and **I/O** interactive plots visualize detailed resource usage, grouped by process. These metrics include succeeded and failed tasks. Use these plots to quickly inspect a pipeline run to determine the resources requested and consumed by each process.
+
+:::tip
+Hover the cursor over each box plot to show more details.
+:::
+
+</TabItem>
+<TabItem value="Configuration" label="Configuration" default>
+
+The **Configuration** tab contains information about the pipeline parameters, Nextflow configuration, and Nextflow command used for the run. 
+
+#### Parameters 
+
+![Parameters](./_images/parameters.png)
+
+The **Parameters** window displays the pipeline parameters configured for the run, with options to view, copy, or download the parameters in Groovy, JSON, or YAML format.
+
+#### Configuration 
+
+![Configuration](./_images/configuration.png)
+
+The **Configuration** window displays the locations of the Nextflow configuration files used for the run, and the resolved configuration resulting from those configuration files. 
+
+#### Command
+
+![Nextflow command](./_images/command.png)
+
+The **Command** window displays the Nextflow command used for the run. 
+
+</TabItem>
+<TabItem value="Datasets" label="Datasets" default>
+
+![Datasets](./_images/datasets.png)
+
+The **Datasets** tab displays information about the [datasets](../data/datasets) used as input for the run. This view is empty if no datasets were selected. 
+
+</TabItem>
+<TabItem value="Reports" label="Reports" default>
+
+![Reports](./_images/reports.png)
+
+The **Reports** tab contains a table with the names, details, and paths to all [reports](../reports/overview) generated by the run, if any were configured. Select a report to open a Data Explorer file preview of the report, with options to open the report in a new tab or download it.
+
+</TabItem>
+<TabItem value="Containers" label="Containers" default>
+
+:::info
+The containers feature is only available from Nextflow 25.03.1-edge. 
+:::
+
+![Containers](./_images/containers.png)
+
+The **Containers** tab displays the details of containers used in the run, if any. Container details shown include:
+
+- **Target image**: Container image used to execute the task.
+- **Source image**: Container image specified in the workflow configuration, if available.
+- **Request ID**: Unique request ID associated with the container.
+- **Request time**: Timestamp when the container request was made.
+- **Build ID**: Unique build ID assigned when the container was provisioned, linked to the Wave container build report.
+- **Mirror ID**: Unique mirror ID assigned when the container was copied between repositories, linked to the Wave mirror report.
+- **Scan ID**: Unique scan ID for the vulnerability security scan of the container, linked to the Wave scan report.
+- **Cached**: Indicates if the container was built during a previous request.
+- **Freeze**: Indicates if the container was provisioned for persistent storage using Wave freeze mode.
+
+</TabItem>
+<TabItem value="Run Info" label="Run Info" default>
+
+The **Run Info** tab contains at-a-glance details about the run, infrastructure, and executor. Hover over the information icon next to a card's name to view a value description. Select the icons next to any run detail values to copy them. 
+
+#### Run details 
+
+![Run details](./_images/run-details.png)
+
+The **Run details** view displays basic run details: 
+
+- **Pipeline** name. Select **View pipeline details** to navigate to the pipeline's details page. 
+- **Workflow repository**. Select **View repository** to navigate to the pipeline Git repository.
+- Run **ID**. 
+- **Run start time**.
+- **Total run duration**.
+- **Launch user**. Select **View user runs** to view a list of the launch user's runs in the same workspace. 
+- **Executor(s)** used for the run (AWS Batch, Azure Batch, etc.).
+- **Revision and Git commit ID**. The pipeline version and Git commit ID associated with the version used for the run. 
+
+#### Infrastructure details 
+
+![Infrastructure details](./_images/infra-details.png)
+
+The **Infrastructure details** view displays compute environment and work directory information:
+
+- **Compute environment** name. Select **Preview** to view a window with basic compute environment details, or **View** to navigate to the compute environment page.
+- **(Provider) operation ID**. The unique identifier for the task submitted to the cloud provider or compute platform, such as an AWS Batch operation ID. 
+- **Work directory**. Select **View** to browse the work directory in Data Explorer.
+- **Compute environment ID**. 
+
+#### Executor(s) details 
+
+![Infrastructure details](./_images/executor-details.png)
+
+The **Executor(s) details** view displays the Nextflow version and Nextflow session ID for the run. 
+
+</TabItem>
+</Tabs>


Reviews:
user: login: justinegeffen
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-11T19:47:53Z
user: login: justinegeffen
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-11T19:48:07Z
user: login: justinegeffen
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-11T19:52:34Z
user: login: justinegeffen
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-11T19:53:15Z
user: login: christopher-hakkaart
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-05-11T21:46:03Z
user: login: christopher-hakkaart
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-05-11T21:56:39Z
user: login: llewellyn-sl
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-12T13:52:06Z
user: login: atsyganov
state: COMMENTED
author_association: NONE
submitted_at: 2025-05-12T14:03:02Z
user: login: llewellyn-sl
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-12T14:04:28Z
user: login: justinegeffen
state: APPROVED
author_association: CONTRIBUTOR
submitted_at: 2025-05-12T17:27:11Z

Review comments:
path: platform-cloud/docs/monitoring/run-details.mdx
user: login: atsyganov
body: ![Screenshot 2025-05-09 at 15 48 47](https://github.com/user-attachments/assets/08a94a16-d510-40bd-8244-c90ab0a1809c)
Some inconsistency in formatting and we are missing Tabs passed Metrics: can this be unified?
created_at: 2025-05-09T15:08:10Z
author_association: NONE
path: platform-cloud/docs/monitoring/run-details.mdx
user: login: atsyganov
body: Can we add screenshot for Containers? I can show how to generate this in your "Showcase" env.
created_at: 2025-05-09T15:13:37Z
author_association: NONE
path: platform-cloud/docs/monitoring/run-details.mdx
user: login: atsyganov
body: ![Screenshot 2025-05-09 at 15 51 56](https://github.com/user-attachments/assets/f6fc670c-5f02-4c44-a21c-a00cf2116fdf)
can we spa formatting to make it unified for all Tabs?
created_at: 2025-05-09T15:16:26Z
author_association: NONE
diff_hunk: @@ -128,40 +157,104 @@ See also: **pcpu**, **cpus**, **peakRss**, and **memory** in the task table.
 
 These metrics measure how efficiently the pipeline is using its compute resources. Low utilization indicates that the pipeline may be over-requesting resources for some tasks.
 
-### Tasks 
+#### Interactive resource plots
 
-The **Tasks** panel shows all the tasks that were executed in a pipeline run.
+![Interactive CPU plot](./_images/interactive-plot.png)
 
-#### Search and filter tasks
+The **CPU**, **Memory**, **Job duration**, and **I/O** interactive plots visualize detailed resource usage, grouped by process. These metrics include succeeded and failed tasks. Use these plots to quickly inspect a pipeline run to determine the resources requested and consumed by each process.
 
-Use the search bar to filter tasks with substrings in the table columns such as **process**, **tag**, **hash**, and **status**. For example, if you enter `succeeded` in the **Search task** field, the table displays only tasks that succeeded.
+:::tip
+Hover the cursor over each box plot to show more details.
+:::
 
-#### Task details
+</TabItem>
+<TabItem value="Configuration" label="Configuration" default>
 
-Select a task in the task table to open the **Task details** dialog. The dialog has three tabs:
+The **Configuration** tab contains information about the pipeline parameters, Nextflow configuration, and Nextflow command used for the run. 
 
-- **About**
-  - **Name**: Process name and tag
-  - **Command**: Task script, defined in the pipeline process
-  - **Status**: Exit code, task status, attempts
-  - **Work directory**: Directory where the task was executed
-  - **Environment**: Environment variables supplied to the task
-  - **Execution time**: Metrics for task submission, start, and completion time
-  - **Resources requested**: Metrics for the resources requested by the task
-  - **Resources used**: Metrics for the resources used by the task
+#### Parameters 
 
-- **Execution log**
+The **Parameters** window displays the pipeline parameters configured for the run, with options to view, copy, or download the parameters in Groovy, JSON, or YAML format.
 
-  The **Execution log** tab provides a real-time log of the selected task's execution. Task execution and other logs (such as `stdout` and `stderr`) are available for download from here, if still available in your compute environment.
+![Interactive CPU plot](./_images/interactive-plot.png)
 
-- **Data Explorer**
+#### Configuration 
 
-  If the pipeline work directory is in cloud storage, this tab shows a [Data Explorer](../data/data-explorer.mdx) view of the task's work directory location with the files associated with the task.
+The **Configuration** window displays the locations of the Nextflow configuration files used for the run, and the resolved configuration resulting from those configuration files. 
 
-### Metrics 
+![Configuration](./_images/configuration.png)
+
+#### Command
+
+The **Command** window displays the Nextflow command used for the run. 
+
+![Nextflow command](./_images/command.png)
+
+</TabItem>
+<TabItem value="Datasets" label="Datasets" default>
+
+The **Datasets** tab displays information about the [datasets](../data/datasets) used as input for the run. This view is empty if no datasets were selected. 
+
+</TabItem>
+<TabItem value="Reports" label="Reports" default>
+
+The **Reports** tab contains a table with the names, details, and paths to all [reports](../reports/overview) generated by the run, if any were configured. Select a report to open a Data Explorer file preview of the report, with options to open the report in a new tab or download it.
+
+![Reports](./_images/reports.png)
+
+</TabItem>
+<TabItem value="Containers" label="Containers" default>
+
+:::info
+The containers feature is only available from Nextflow 25.03.1-edge. 
+:::
+
+![Containers](./_images/containers.png)
+
+The **Containers** tab displays the details of containers used in the run, if any. Container details shown include:
+
+- **Target image**: Container image used to execute the task.
+- **Source image**: Container image specified in the workflow configuration, if available.
+- **Request ID**: Unique request ID associated with the container.
+- **Request time**: Timestamp when the container request was made.
+- **Build ID**: Unique build ID assigned when the container was provisioned, linked to the Wave container build report.
+- **Mirror ID**: Unique mirror ID assigned when the container was copied between repositories, linked to the Wave mirror report.
+- **Scan ID**: Unique scan ID for the vulnerability security scan of the container, linked to the Wave scan report.
+- **Cached**: Indicates if the container was built during a previous request.
+- **Freeze**: Indicates if the container was provisioned for persistent storage using Wave freeze mode.
+
+</TabItem>
+<TabItem value="Run Info" label="Run Info" default>
+
+The **Run Info** tab contains at-a-glance details about the run, infrastructure, and executor. Hover over the information icon next to a card's name to view a value description. Select the icons next to any run detail values to copy them. 
+
+#### Run details 
+
+The **Run details** view displays basic run details: 
+
+- **Pipeline** name. Select **View pipeline details** to navigate to the pipeline's details page. 
+- **Workflow repository**. Select **View repository** to navigate to the pipeline Git repository.
+- Run **ID**. 
+- **Run start time**.
+- **Total run duration**.
+- **Launch user**. Select **View user runs** to view a list of the launch user's runs in the same workspace. 
+- **Executor(s)** used for the run (AWS Batch, Azure Batch, etc.).
+- **Revision and Git commit ID**. The pipeline version and Git commit ID associated with the version used for the run. 
+
+#### Infrastructure details 
+
+The **Infrastructure details** view displays compute environment and work directory information:
+
+- **Compute environment** name. Select **Preview** to view a window with basic compute environment details, or **View** to navigate to the compute environment page.
+- **(Provider) operation ID**. The unique identifier for the task submitted to the cloud provider or compute platform, such as an AWS Batch operation ID. 
+- **Work directory**. Select **View** to browse the work directory in Data Explorer.
+- **Compute environment ID**. 
path: platform-cloud/docs/monitoring/run-details.mdx
user: login: atsyganov
body: Add this to Compute Environment ID: "is a unique identifier for cloud provider for a defined set of computing resources used to run jobs or tasks."
created_at: 2025-05-09T15:24:37Z
author_association: NONE
diff_hunk: @@ -0,0 +1,262 @@
+---
+title: "Run details"
+description: "Monitoring a Nextflow pipeline executed through Seqera Platform."
+date: "21 Apr 2023"
+tags: [logging, monitoring, execution]
+---
+
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
+Select a workflow run from the **Runs** list to open a run details page. 
+
+![Run details and progress overview](./_images/progress-bar.png)
+
+The top of the page contains basic run details and a progress overview for an at-a-glance view of the run's status:
+- View and copy the run ID, pipeline name and repository, pipeline work directory, compute environment, and launch date. 
+- Select the star icon to favorite the run and find it more easily via a filter view in the runs list later. 
+- Use the options menu to apply labels, relaunch, resume, or delete the run, or to save the run as a new pipeline. 
+
+Select the tabs below the workflow run progress bar to view further run details:
+- **Tasks**: View the status and progress of pipeline tasks and [processes](#processes), including extensive [task details](#tasks)
+- **Logs**: View and download the pipeline run's execution log
+- **Metrics**: View resource [metrics](#metrics) for the run 
+- 
path: platform-cloud/docs/monitoring/run-details.md
user: login: justinegeffen
body: Missing a list item?
created_at: 2025-05-11T19:47:52Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,262 @@
+---
+title: "Run details"
+description: "Monitoring a Nextflow pipeline executed through Seqera Platform."
+date: "21 Apr 2023"
+tags: [logging, monitoring, execution]
+---
+
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
+Select a workflow run from the **Runs** list to open a run details page. 
+
+![Run details and progress overview](./_images/progress-bar.png)
+
+The top of the page contains basic run details and a progress overview for an at-a-glance view of the run's status:
+- View and copy the run ID, pipeline name and repository, pipeline work directory, compute environment, and launch date. 
+- Select the star icon to favorite the run and find it more easily via a filter view in the runs list later. 
+- Use the options menu to apply labels, relaunch, resume, or delete the run, or to save the run as a new pipeline. 
+
+Select the tabs below the workflow run progress bar to view further run details:
+- **Tasks**: View the status and progress of pipeline tasks and [processes](#processes), including extensive [task details](#tasks)
+- **Logs**: View and download the pipeline run's execution log
+- **Metrics**: View resource [metrics](#metrics) for the run 
+- 
+- [Run information](#run-information) with real-time Nextflow execution details
+- [General summary](#general-summary) and [task status](#task-status)
+- List of pipeline 
path: platform-cloud/docs/monitoring/run-details.md
user: login: justinegeffen
body: ```suggestion
- List of pipelines
```
created_at: 2025-05-11T19:48:07Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,262 @@
+---
+title: "Run details"
+description: "Monitoring a Nextflow pipeline executed through Seqera Platform."
+date: "21 Apr 2023"
+tags: [logging, monitoring, execution]
+---
+
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
+Select a workflow run from the **Runs** list to open a run details page. 
+
+![Run details and progress overview](./_images/progress-bar.png)
+
+The top of the page contains basic run details and a progress overview for an at-a-glance view of the run's status:
+- View and copy the run ID, pipeline name and repository, pipeline work directory, compute environment, and launch date. 
+- Select the star icon to favorite the run and find it more easily via a filter view in the runs list later. 
+- Use the options menu to apply labels, relaunch, resume, or delete the run, or to save the run as a new pipeline. 
+
+Select the tabs below the workflow run progress bar to view further run details:
+- **Tasks**: View the status and progress of pipeline tasks and [processes](#processes), including extensive [task details](#tasks)
+- **Logs**: View and download the pipeline run's execution log
+- **Metrics**: View resource [metrics](#metrics) for the run 
path: platform-cloud/docs/monitoring/run-details.md
user: login: justinegeffen
body: These three make sense as they're tabs listed in the screenshot.

However, the following 4 points don't have a corresponding tab and in this context it's not clear what they're referring to. If they're referring to content in a tab, I'd precede the explanation with the tab name just for clarity.
created_at: 2025-05-11T19:52:34Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,262 @@
+---
+title: "Run details"
+description: "Monitoring a Nextflow pipeline executed through Seqera Platform."
+date: "21 Apr 2023"
+tags: [logging, monitoring, execution]
+---
+
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
+Select a workflow run from the **Runs** list to open a run details page. 
+
+![Run details and progress overview](./_images/progress-bar.png)
+
+The top of the page contains basic run details and a progress overview for an at-a-glance view of the run's status:
+- View and copy the run ID, pipeline name and repository, pipeline work directory, compute environment, and launch date. 
+- Select the star icon to favorite the run and find it more easily via a filter view in the runs list later. 
+- Use the options menu to apply labels, relaunch, resume, or delete the run, or to save the run as a new pipeline. 
+
+Select the tabs below the workflow run progress bar to view further run details:
+- **Tasks**: View the status and progress of pipeline tasks and [processes](#processes), including extensive [task details](#tasks)
+- **Logs**: View and download the pipeline run's execution log
+- **Metrics**: View resource [metrics](#metrics) for the run 
+- 
+- [Run information](#run-information) with real-time Nextflow execution details
+- [General summary](#general-summary) and [task status](#task-status)
+- List of pipeline 
+- [Aggregated stats](#aggregate-stats), [load](#load), and [utilization](#utilization)
+
+<Tabs>
+<TabItem value="Tasks" label="Tasks" default>
+
+![Task status overview](./_images/task-status-tiles.png)
+
+The cards at the top of the **Tasks** tab provide a real-time status of all tasks in the pipeline run:
path: platform-cloud/docs/monitoring/run-details.md
user: login: justinegeffen
body: I propose removing the screenshot above and having a screenshot of just the icons from the Tasks tab over here. 
created_at: 2025-05-11T19:53:15Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,262 @@
+---
+title: "Run details"
+description: "Monitoring a Nextflow pipeline executed through Seqera Platform."
+date: "21 Apr 2023"
+tags: [logging, monitoring, execution]
+---
+
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
+Select a workflow run from the **Runs** list to open a run details page. 
+
+![Run details and progress overview](./_images/progress-bar.png)
+
+The top of the page contains basic run details and a progress overview for an at-a-glance view of the run's status:
+- View and copy the run ID, pipeline name and repository, pipeline work directory, compute environment, and launch date. 
+- Select the star icon to favorite the run and find it more easily via a filter view in the runs list later. 
+- Use the options menu to apply labels, relaunch, resume, or delete the run, or to save the run as a new pipeline. 
+
+Select the tabs below the workflow run progress bar to view further run details:
+- **Tasks**: View the status and progress of pipeline tasks and [processes](#processes), including extensive [task details](#tasks)
+- **Logs**: View and download the pipeline run's execution log
+- **Metrics**: View resource [metrics](#metrics) for the run 
+- 
+- [Run information](#run-information) with real-time Nextflow execution details
+- [General summary](#general-summary) and [task status](#task-status)
+- List of pipeline 
+- [Aggregated stats](#aggregate-stats), [load](#load), and [utilization](#utilization)
+
+<Tabs>
+<TabItem value="Tasks" label="Tasks" default>
+
+![Task status overview](./_images/task-status-tiles.png)
+
+The cards at the top of the **Tasks** tab provide a real-time status of all tasks in the pipeline run:
+
+- **Pending**: The task has been created, but not yet submitted to an executor.
+- **Submitted**: The task has been submitted to an executor, but is not yet running.
+- **Running**: The task has been launched by an executor (the precise definition of "running" may vary for each executor).
+- **Cached**: A previous (and valid) execution of the task was found and used instead of executing the task again. See [Cache and resume](../launch/cache-resume.mdx).
+- **Succeeded**: The task completed successfully.
+- **Failed**: The task failed.
+- **Aborted**: The task was submitted, but the run was cancelled or failed before the task could begin.
path: platform-cloud/docs/monitoring/run-details.md
user: login: christopher-hakkaart
body: ```suggestion
- **Pending**: The task has been created, but not yet submitted to an executor
- **Submitted**: The task has been submitted to an executor, but is not yet running
- **Running**: The task has been launched by an executor (the precise definition of "running" may vary for each executor)
- **Cached**: A previous (and valid) execution of the task was found and used instead of executing the task again. See [Cache and resume](../launch/cache-resume.mdx)
- **Succeeded**: The task completed successfully
- **Failed**: The task failed
- **Aborted**: The task was submitted, but the run was cancelled or failed before the task could begin
```
created_at: 2025-05-11T21:46:02Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,262 @@
+---
+title: "Run details"
+description: "Monitoring a Nextflow pipeline executed through Seqera Platform."
+date: "21 Apr 2023"
+tags: [logging, monitoring, execution]
+---
+
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
+Select a workflow run from the **Runs** list to open a run details page. 
+
+![Run details and progress overview](./_images/progress-bar.png)
+
+The top of the page contains basic run details and a progress overview for an at-a-glance view of the run's status:
+- View and copy the run ID, pipeline name and repository, pipeline work directory, compute environment, and launch date. 
+- Select the star icon to favorite the run and find it more easily via a filter view in the runs list later. 
+- Use the options menu to apply labels, relaunch, resume, or delete the run, or to save the run as a new pipeline. 
+
+Select the tabs below the workflow run progress bar to view further run details:
+- **Tasks**: View the status and progress of pipeline tasks and [processes](#processes), including extensive [task details](#tasks)
+- **Logs**: View and download the pipeline run's execution log
+- **Metrics**: View resource [metrics](#metrics) for the run 
+- 
+- [Run information](#run-information) with real-time Nextflow execution details
+- [General summary](#general-summary) and [task status](#task-status)
+- List of pipeline 
+- [Aggregated stats](#aggregate-stats), [load](#load), and [utilization](#utilization)
+
+<Tabs>
+<TabItem value="Tasks" label="Tasks" default>
+
+![Task status overview](./_images/task-status-tiles.png)
+
+The cards at the top of the **Tasks** tab provide a real-time status of all tasks in the pipeline run:
+
+- **Pending**: The task has been created, but not yet submitted to an executor.
+- **Submitted**: The task has been submitted to an executor, but is not yet running.
+- **Running**: The task has been launched by an executor (the precise definition of "running" may vary for each executor).
+- **Cached**: A previous (and valid) execution of the task was found and used instead of executing the task again. See [Cache and resume](../launch/cache-resume.mdx).
+- **Succeeded**: The task completed successfully.
+- **Failed**: The task failed.
+- **Aborted**: The task was submitted, but the run was cancelled or failed before the task could begin.
+
+### Processes 
+
+The **Processes** panel displays the status of each process in a pipeline run. In Nextflow, a process is an individual step in a pipeline, while a task is a particular invocation of a process for given input data. In the panel, each process is shown with a progress bar indicating how many tasks have been completed for that process.
+
+The progress bar is color-coded based on task status (**created**, **submitted**, **completed**, **failed**).
+
+Select a process to navigate to the [Tasks](#tasks) panel and filter the table contents by the selected process.
+
+### Tasks 
+
+The **Tasks** panel shows all the tasks that were executed in the run.
+
+Use the search bar to filter tasks with substrings in the table columns such as **process**, **tag**, **hash**, and **status**. For example, if you enter `succeeded` in the **Search task** field, the table displays only tasks that succeeded.
+
+#### Task details
+
+![Task details](./_images/task-details.png)
+
+Select a task in the task table to open the **Task details** dialog. The dialog has three tabs:
+
+- **About**
+  - **Name**: Process name and tag
+  - **Command**: Task script, defined in the pipeline process
+  - **Status**: Exit code, task status, attempts
+  - **Work directory**: Directory where the task was executed
+  - **Environment**: Environment variables supplied to the task
+  - **Execution time**: Metrics for task submission, start, and completion time
+  - **Resources requested**: Metrics for the resources requested by the task
+  - **Resources used**: Metrics for the resources used by the task
+
+- **Execution log**
+
+  The **Execution log** tab provides a real-time log of the selected task's execution. Task execution and other logs (such as `stdout` and `stderr`) are available for download from here, if still available in your compute environment.
path: platform-cloud/docs/monitoring/run-details.md
user: login: christopher-hakkaart
body: ```suggestion
  The **Execution log** tab provides a real-time log of the selected task's execution. Task execution and other logs (such as `stdout` and `stderr`) are available for download if they are still available in your compute environment.
```
Not a blocker, but can "still available in your compute environment" be clarified? Should when they are not available be described?
created_at: 2025-05-11T21:56:38Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,262 @@
+---
+title: "Run details"
+description: "Monitoring a Nextflow pipeline executed through Seqera Platform."
+date: "21 Apr 2023"
+tags: [logging, monitoring, execution]
+---
+
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
+Select a workflow run from the **Runs** list to open a run details page. 
+
+![Run details and progress overview](./_images/progress-bar.png)
+
+The top of the page contains basic run details and a progress overview for an at-a-glance view of the run's status:
+- View and copy the run ID, pipeline name and repository, pipeline work directory, compute environment, and launch date. 
+- Select the star icon to favorite the run and find it more easily via a filter view in the runs list later. 
+- Use the options menu to apply labels, relaunch, resume, or delete the run, or to save the run as a new pipeline. 
+
+Select the tabs below the workflow run progress bar to view further run details:
+- **Tasks**: View the status and progress of pipeline tasks and [processes](#processes), including extensive [task details](#tasks)
+- **Logs**: View and download the pipeline run's execution log
+- **Metrics**: View resource [metrics](#metrics) for the run 
path: platform-cloud/docs/monitoring/run-details.md
user: login: llewellyn-sl
body: Marked the PR ready for review before fixing this. Thanks!
created_at: 2025-05-12T13:52:06Z
author_association: CONTRIBUTOR
path: platform-cloud/docs/monitoring/run-details.mdx
user: login: llewellyn-sl
body: Already done, thanks
created_at: 2025-05-12T14:04:28Z
author_association: CONTRIBUTOR

PR comments:
user: login: netlify[bot]
created_at: 2025-05-02T18:58:34Z
body: ### <span aria-hidden="true">✅</span> Deploy Preview for *seqera-docs* ready!


|  Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 6bb76dc05006f9456292b547b6e4f141c9c22417 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/sites/seqera-docs/deploys/682235c40d788000089232b9 |
|<span aria-hidden="true">😎</span> Deploy Preview | [https://deploy-preview-581--seqera-docs.netlify.app](https://deploy-preview-581--seqera-docs.netlify.app) |
|<span aria-hidden="true">📱</span> Preview on mobile | <details><summary> Toggle QR Code... </summary><br /><br />![QR Code](https://app.netlify.com/qr-code/eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJ1cmwiOiJodHRwczovL2RlcGxveS1wcmV2aWV3LTU4MS0tc2VxZXJhLWRvY3MubmV0bGlmeS5hcHAifQ.zDxfdCF3jI6AxQ-IYBVLvuEnF4byoppFUleTWuG4-fI)<br /><br />_Use your smartphone camera to open QR code link._</details> |
---
<!-- [seqera-docs Preview](https://deploy-preview-581--seqera-docs.netlify.app) -->
_To edit notification comments on pull requests, go to your [Netlify site configuration](https://app.netlify.com/sites/seqera-docs/configuration/notifications#deploy-webhooks)._
author_association: NONE
user: login: justinegeffen
created_at: 2025-05-11T19:57:20Z
body: This is looking awesome! I love the tabbed content. Ping me for a second pass once you've had all the feedback. 
author_association: CONTRIBUTOR
user: login: christopher-hakkaart
created_at: 2025-05-11T22:00:40Z
body: ⚠️ Also noted that the tabs aren't showing in the preview; everything below the tabbed table is missing.
author_association: MEMBER
user: login: atsyganov
created_at: 2025-05-12T16:36:30Z
body: all fine from my point of view
author_association: NONE