Files
wehub-resource-sync 4b6817381b
Benchmark image — build + push to ECR (any adapter) / build + push (push) Waiting to run
CI / quality (ubuntu-latest) (push) Waiting to run
CI / test (tools-runtime) (push) Waiting to run
CI / test (e2e-general) (push) Waiting to run
CI / test (cli-runtime) (push) Waiting to run
CI / test (e2e-provider-and-openclaw) (push) Waiting to run
CI / test (integrations-and-misc) (push) Waiting to run
CI / coverage-report (push) Blocked by required conditions
CI / test-kubernetes (push) Waiting to run
CI / should-run-thorough (push) Waiting to run
CI / test-thorough (cloudwatch-demo) (push) Blocked by required conditions
CI / test-thorough (flink-ecs) (push) Blocked by required conditions
CI / test-thorough (upstream-lambda) (push) Blocked by required conditions
CI / test-thorough (prefect-ecs-fargate) (push) Blocked by required conditions
CodeQL / Analyze (python) (push) Waiting to run
Release / build-binaries (zip, opensre.exe, onefile, windows-latest, windows-x64) (push) Blocked by required conditions
Release / publish-release (push) Blocked by required conditions
Release / publish-main-release (push) Blocked by required conditions
Release / prepare (push) Waiting to run
Release / verify (push) Blocked by required conditions
Release / build-python-dist (push) Blocked by required conditions
Release / build-binaries (tar.gz, opensre, onedir, macos-15-intel, darwin-x64) (push) Blocked by required conditions
Release / build-binaries (tar.gz, opensre, onedir, macos-latest, darwin-arm64) (push) Blocked by required conditions
Release / build-binaries (tar.gz, opensre, onedir, ubuntu-22.04, linux-x64) (push) Blocked by required conditions
Release / build-binaries (tar.gz, opensre, onedir, ubuntu-22.04-arm, linux-arm64) (push) Blocked by required conditions
Synthetic Deterministic Tests / Synthetic offline (deterministic) (push) Waiting to run
Interactive Shell Live (PR + post-merge) / turn-checks (no-LLM) (push) Waiting to run
Interactive Shell Live (PR + post-merge) / turn-live shard ${{ matrix.shard_index }} (push) Waiting to run
CI (OpenClaw E2E) / openclaw test (push) Has been cancelled
chore: import upstream snapshot with attribution
2026-07-13 13:10:45 +08:00

130 lines
5.9 KiB
Plaintext
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
---
title: 'Viewing Task Status'
description: 'Learn how to monitor and view the status of your tasks in Tracer'
---
On this page, we will explain how you can see the status of your tasks within a specific pipeline run.<br/>
<Info>If you have not yet run a pipeline, please refer to the [quickstart](/quickstart) to get started.</Info>
When executed correctly, you should be able to see the following screen in the Tracer dashboard:
<video
autoPlay
loop
muted
playsInline
style={{ width: '100%', maxWidth: '100%' }}
>
<source src="/images/tutorials/view-task-status/View-Tool-Details.mp4" type="video/mp4" />
Your browser does not support the video tag.
</video>
<Tip>Tracer updates task status in real time, so you can monitor progress without refreshing the page.</Tip>
Tracer provides detailed visibility into task execution, allowing you to track progress, identify bottlenecks, and ensure your workflows are running smoothly.
## Accessing Task Status
<Steps>
<Step title="Navigate to Pipelines Overview">
Open the Tracer dashboard and select the **"Pipelines"** tab next to "Overview". This will show you all the pipelines that have been run.
![General Overview](/images/tutorials/view-task-status/1.png)
<Tip>When hovering over the pipeline runs, you get more information about what pipelines have been run or are currently running.</Tip>
</Step>
<Step title="Go to your Specific Pipeline">
Access your specific pipeline by clicking on the pipeline name. You can recognize the pipelines which are currently running by the blue dot next to the pipeline name.
![Pipeline Overview](/images/tutorials/view-task-status/2.png)
</Step>
<Step title="Select the Correct Run">
As you will most likely check the current or latest run of the selected pipeline, you can click the blue link **"Latest Run"** to go to the latest run.
If you are searching for an older run, you can click on the **"Pipeline Runs"** box in the bottom left corner of the screen. This will show you all runs, where you can select the run you are looking for.
![Pipeline Runs](/images/tutorials/view-task-status/3.png)
</Step>
<Step title="Navigate to Tools">
Here, you get the first high-level overview of the pipeline run. You can see the main metrics, runtime and cost as well as the automatic logs with warnings and failure indicators.
To go to the task status, click on the **"Tools"** tab next to "Overview". This will show you the status of all tasks within this pipeline run.
![Runs Overview](/images/tutorials/view-task-status/4.png)
</Step>
<Step title="Investigate Task Status">
The tool visualizer shows you the status of all tasks within this pipeline run:
- **Bar width** indicates the runtime of the task
- **Bar color** indicates the status: Grey (running), Green (completed), Red (failed)
![Tool Visualiser](/images/tutorials/view-task-status/5.png)
<Info>In the image above, all tools are completed as indicated by the green bars.</Info>
**When hovering over a specific task**, you can see the status, runtime, and the exact moment the task started. By clicking the bar, you can dig one level deeper to see the metrics, runtime, cost, and logs with warnings and failure indicators.
![Running Hover](/images/tutorials/view-task-status/6.png)
<Info>In the image above, the task is still running as indicated by the grey bar and has been running for exactly 30.591s.</Info>
**For a more detailed overview**, click on the **"Detailed"** button in the top right corner of the screen. This will list all tools in a table showing status, command, start time, runtime, max RAM, max CPU, max Disk I/O, and end time.
![Detailed View](/images/tutorials/view-task-status/7.png)
<Info>In the image above, you can see that one task is still running as indicated by the "Running" status, while the others are successfully completed.</Info>
</Step>
<Step title="Tool Specific Metrics">
Here, you can see the run-specific metrics including:
- **Tool ID** - Unique identifier for the task
- **Run Name** - Name of the current run
- **Pipeline Name** - Name of the parent pipeline
- **AI Insights** - Intelligent analysis and recommendations
- **Runtime Metrics** - CPU, memory, and I/O usage
You can also compare this task's performance to previous runs.
![Tool Metrics](/images/tutorials/view-task-status/8.png)
</Step>
</Steps>
**After these steps, youll have live visibility into task progress, metrics, and logs for your pipeline run.**
## Task Status Indicators
Tracer displays tasks with the following status indicators:
| Status | Description | Color Used to Indicate |
|--------|-------------| ----------------------|
| **Running** | Task is currently executing | Grey |
| **Completed** | Task finished successfully | Green |
| **Failed** | Task encountered an error | Red |
## Task Metrics
When viewing a task, you'll see detailed information including:
| Category | Metric | Description |
|----------|--------|-------------|
| **Status & Timing** | Status | Current state of the task (Running, Completed, Failed) |
| | Runtime | Total execution time |
| | Start Time | When the task began |
| | End Time | When the task completed (if applicable) |
| **Resource Usage** | CPU | Processor utilization |
| | RAM Memory | Memory consumption |
| | Disk I/O | Read/write operations |
| | Network I/O | Network traffic |
| **Logs & Debugging** | Automatic Logs | Standard output and deep system-level logs captured |
| | Warnings | Highlighted warnings and failure indicators |
| **Additional Information** | Command | The exact command executed |
| | Historical Comparison | Performance comparison with previous runs of this task |
## Next Steps
How to get even more out of Tracer's capabilities:
<Card title="Investigating Task Failures" href="/tutorials/investigating-task-failures">
Learn how to debug failed tasks
</Card>