View Pipeline and Pipeline Run details
Click any pipeline name across SolarWinds Observability SaaS to open its details page in the Entity Explorer. The page contains three tabs:
-
Overview: Shows the pipeline health, alerts, latest and failed executions, and a metadata panel.
-
Runs: Lists every execution of the pipeline within the selected filters and time range.
-
Metrics: Lists all metrics collected for the pipeline.
If service level objectives are available, an SLO tab is added.
The toolbar includes the time range selector, live polling toggle, entity search, and filters for narrowing runs by Result, Branch Name, and Pull Request.
Overview
The Overview tab shows the pipeline health, alerts, executions, and a metadata panel:
-
Health: Current health state and a timeline of health state transitions over the selected time range.
-
Active Alerts: Alerts currently triggered on this pipeline entity.
-
Latest Execution: Span waterfall of the most recent run, showing nested jobs and steps. Toggle between span chart and tree views, or expand to inspect deeper hierarchies.
-
Failed Executions: A histogram of failed runs bucketed over time, indicating whether failures are constant or clustered around specific code releases.
-
Metadata panel: Displays basic tags, CI/CD and VCS provider links, and an SWO Integration link leading to the connected GitHub organization under Settings.
Runs
The Runs tab lists every execution of the pipeline within the selected filters and time range. Three summary widgets sit above the table:
-
Success Rate donut: Proportional breakdown of the following categories:
-
Success
-
Failure (includes
failed,timed out, andstartup failure) -
Canceled or skipped
-
Running
-
Other (for example,
action required)If there are no runs in a category, the category is not displayed in the donut.
-
-
Average Duration: Mean run duration, plotted with a threshold line indicating the 30-day 95th percentile (p95) benchmark (displayed when at least five data points exist).
-
Duration Distribution: Spread of run execution times to distinguish uniformly slow pipelines from pipelines with occasional long outliers.
The runs table includes:
-
Result: Success, Failure, Canceled, Skipped, Timed Out, or Startup Failure. (Other GitHub conclusions, such as neutral, action required, or stale, display as Unknown).
-
Name: Pull request title (for PR-triggered runs), workflow run number, or GitHub run ID. Links to the run's distributed trace.
-
Branch / Commit: Direct links to the branch and commit in GitHub.
-
Duration: Total execution duration.
-
Images: Count of container images built by the run, or Not Available if none was detected.
-
Last Seen: Timestamp when the run finished updating.
Analyze runs with distributed tracing
Each pipeline run is recorded as a distributed trace:
-
Root span: The overall workflow run.
-
Child spans: Individual jobs within the workflow.
-
Grandchild spans: Execution steps inside each job.
To inspect a run trace:
-
Click any run name on the Runs tab, or navigate to Analyze > Traces and choose the Traced CI/CD Pipeline Runs view.
-
In the waterfall:
-
View the order in which jobs executed and identify parallel vs. sequential tasks.
-
Determine which job contributed most to the overall run duration.
-
Identify the exact step where a failing run halted.
-
-
Select any span to view its attributes, including runner name, job result, and the link to the job log in GitHub.
SolarWinds Observability does not collect GitHub step logs or error messages. A failed run, job, or step is marked as an error and shows only the GitHub result, for example, failure. To inspect build logs, open the failed job in the waterfall and follow the job link to GitHub.
Container images and Kubernetes deployments
Pipeline runs can be correlated with the container images they build and the Kubernetes workloads that deploy them:
-
Requirements: Container images must be built with Docker Buildx / BuildKit so that image digest metadata (containerimage.digest) is captured in build logs. The deploying Kubernetes cluster must be monitored by SolarWinds Observability SaaS.
-
Where correlation appears:
-
Images column: On the pipeline's Runs tab, shows the number of container images produced by that run.
-
Events → Deployments: The Pipeline Run column links directly to the run trace that built the deployed image. (A dash — indicates no connected pipeline run produced the image). Deployments are checked every 15 minutes.
-
Kubernetes Deployment overview charts: Chart annotations include a Pipeline Run entry alongside image tags and commit hashes.
-
Metrics
The Metrics tab lists all metrics collected for the pipeline with their unit, description, and last reported timestamp. Click any metric to plot it in the Metrics Explorer. Turn on Include Metrics Without Data to view metrics that have not reported values in the current time window.