Documentation forSolarWinds Observability SaaS

Troubleshoot Software Delivery

No pipelines appear after connecting GitHub

SolarWinds Observability SaaS only collects runs that GitHub reports after the connection is established. Past runs are not imported.

Resolve the issue:

Trigger each workflow in GitHub to execute once after connecting. Pipelines appear automatically after their first run. See Connect GitHub.

A pipeline is missing from the list

The list displays only pipelines that reported telemetry within the selected time range.

Resolve the issue:

Adjust the time range selector to an interval that includes the pipeline's active runs (for example, from Past 7 days to Past 30 days). See Pipelines.

Connection wizard times out after 3 minutes

The connection request is waiting for owner approval in GitHub, or an existing connection was updated instead of adding a new one.

Resolve the issue:

  1. In SolarWinds Observability SaaS, click Settings > GitHub > Integrations.

  2. Verify the connection status.

  3. If the entry is marked Pending, have an organization owner authorize the app in GitHub.

See Manage GitHub connections.

GitHub reports successful connection, but no data arrives

The GitHub organization is already connected to another SolarWinds Observability SaaS organization. An app installation sends telemetry to only one organization, and the first organization to claim it keeps it.

Resolve the issue:

Access the SolarWinds Observability SaaS organization where the integration was first connected, or uninstall the app in GitHub and reconnect it from this organization. See Remove GitHub connections.

Integration is listed as Pending

The connection entry has no repositories attached, typically because the installation request is awaiting approval from an organization owner in GitHub.

Resolve the issue:

Contact an owner of the GitHub organization to approve the app installation request in GitHub. See Configure Software Delivery.

The Images column displays Not Available

Container images were built without Docker Buildx / BuildKit metadata.

Resolve the issue:

Build images using Docker Buildx / BuildKit so that image manifest digests (containerimage.digest) are output to build logs. See Container images and Kubernetes deployments.

Deployments page shows "—" under Pipeline Run

The deployed container image was not built by a connected pipeline, or the cluster is unmonitored.

Resolve the issue:

Ensure the Kubernetes cluster is monitored by SolarWinds Observability SaaS and the image was built by a connected pipeline run using BuildKit.

Pipeline health displays Unknown

The pipeline has not run within the rolling 24-hour calculation window.

Resolve the issue: 

The health score requires at least one run in the past 24 hours. Trigger a run to recalculate health.

Pipeline health is Bad even though recent runs succeeded

An active Critical alert exists on the CI/CD Pipeline entity.

Resolve the issue: 

Inspect the Active Alerts widget on the PipelineDetails Overview tab. Critical alerts override good scores until resolved.

Success or failure rates differ between screens

Different screens and widgets categorize run outcomes differently depending on their analytical purpose.

Review the run counting reference in How runs are calculated to see how each view handles cancelled, skipped, or startup-failure runs.

A run’s Name shows a long GitHub run ID instead of the run number

Some runs record the GitHub run ID instead of the pull request title or sequential run number.

This is expected behavior for some runs; the name still links directly to the run's distributed trace. See Runs.

Failed run trace shows error status without error message

SolarWinds Observability SaaS does not collect raw terminal logs or step error strings.

Resolve the issue:

Open the failed job in the waterfall and follow the cicd.pipeline.task.run.url.full link to view execution logs in GitHub. See View Pipeline and Pipeline Run details.

Last Seen updates even when the pipeline has not run

Health scores recalculate every 5 minutes for active pipelines, which refreshes the entity's Last Seen timestamp.

Resolve the issue:

To see the actual last run time, review the inspector panel or open the pipeline's Runs tab. See Pipelines.

GitHub continues sending events after integration was deleted

Deleting the integration in SolarWinds Observability SaaS Settings removes local configurations but does not uninstall the app in GitHub.

Resolve the issue: 

  1. Navigate to Settings > GitHub Apps in your GitHub organization.

  2. Click Uninstall on the SolarWinds Observability app.

See Remove GitHub connections.