CI Visibility Troubleshooting
CI Visibility is not available in the selected site () at this time.
Overview
This page provides information to help you troubleshot issues with CI Visibility. If you need additional help, contact Datadog Support.
Your Jenkins instance is instrumented, but Datadog isn’t showing any data
- Make sure that at least one pipeline has finished executing. Pipeline execution information is only sent after the pipeline has finished.
- Make sure the Datadog Agent host is properly configured and is reachable by the Datadog Plugin. You can test connectivity by clicking on the Check connectivity with the Datadog Agent button on the Jenkins plugin configuration UI.
- Check for any errors in the Jenkins logs. You can enable debug-level logs for the Datadog plugin by creating a
logging.properties file and adding the line: org.datadog.level = ALL.
Pipeline not found
A “Pipeline not found” message is shown when you click on incomplete data coming from an in-progress pipeline for those CI providers that do not support running pipelines. Data is received progressively for stages, jobs, or custom commands. Wait until the pipeline has finished and try again.
Missing pipelines on the Pipelines page
The pipeline page only displays pipelines with no Git information, or pipelines with Git information which belong to the default branch of the Git repository.
Missing stages or jobs in summary tables
Missing stages or jobs in the Pipeline Details page might be due to a wrong configuration. Make sure that the pipeline name stored in the stage or job executions matches the same name of their parent pipeline. If you are using custom pipelines, refer to the public API endpoint specification.
Missing variables in Gitlab pipelines
User-defined variables in Gitlab should be reported in the field @ci.parameters in CI Visibility. However, this information is only present in some cases like downstream pipelines, and may be missing for the rest of the cases since Gitlab does not always report this information to Datadog.
Limitations on running pipelines
Delivery of webhook events is not guaranteed by CI providers
Running pipelines support relies on data sent from CI providers indicating execution status. If this data is not available, executions marked as Running in Datadog may have already finished.
Maximum duration for a pipeline execution
A pipeline execution can maintain Running status for a maximum of three days. If it is still running after that time, the pipeline execution does not appear in CI Visibility. If a pipeline execution finishes after three days, the finished pipeline execution appears in CI Visibility with its correspondent final status (Success, Error, Canceled, Skipped) and with the correct duration.
Limitations on finished jobs from pipelines
Job data has a three-day limit to be processed after completion. If a pipeline includes jobs that finish more than three days before the pipeline is received, those jobs are not processed and do not appear in CI Visibility.
Further reading
Additional helpful documentation, links, and articles:
