diff --git a/content/en/continuous_integration/guides/identify_highest_impact_jobs_with_critical_path.md b/content/en/continuous_integration/guides/identify_highest_impact_jobs_with_critical_path.md index 2f360f09ebfd5..bef8799e04853 100644 --- a/content/en/continuous_integration/guides/identify_highest_impact_jobs_with_critical_path.md +++ b/content/en/continuous_integration/guides/identify_highest_impact_jobs_with_critical_path.md @@ -28,15 +28,6 @@ The exclusive time of a job on the critical path represents the amount of time t If a CI job `job1` is on the critical path with a duration of 100ms and runs in parallel with a CI job `job2`, which has a duration of 80ms, the exclusive time of `job1` on the critical path is 20ms. This means that reducing the duration of the `job1` by more than 20ms would still only decrease the overall pipeline duration by 20ms. -### Supported CI providers - -Filtering and computing the Exclusive Time of CI jobs on the critical path is available for the following CI providers: -* [GitLab][3] - -
If you are interested in critical path but your CI provider is not supported yet, fill out this form.
- -Even without Filtering and computing Exclusive Time, you can still [highlight which CI jobs are on the critical path][4] using the Pipeline Execution detail view across all CI providers. - ## Identify the key CI jobs to improve your CI pipeline ### Using the facet @@ -50,7 +41,7 @@ Notice that these facets are only available using the `ci_level:job` in your que ### Using the dashboard template You can also import the [CI Visibility - Critical Path][1] dashboard template: -- Open the [civisibility-critical-path-gitlab-dashboard.json][1] dashboard template and copy the content in the clipboard. +- Open the [civisibility-critical-path-dashboard.json][1] dashboard template and copy the content in the clipboard. - Create a [New Dashboard][2] in Datadog. - Paste the copied content in the new dashboard. - Save the dashboard. @@ -77,7 +68,7 @@ Since we know this CI job is on the critical path 43.5% of the time, we could po {{< partial name="whats-next/whats-next.html" >}} -[1]: /resources/json/civisibility-critical-path-gitlab-dashboard.json +[1]: /resources/json/civisibility-critical-path-dashboard.json [2]: /dashboards/ [3]: /continuous_integration/pipelines/gitlab/?tab=gitlabcom [4]: /continuous_integration/search/#highlight-critical-path \ No newline at end of file diff --git a/content/en/continuous_integration/pipelines/_index.md b/content/en/continuous_integration/pipelines/_index.md index 0848f9147a48d..c25301956dac1 100644 --- a/content/en/continuous_integration/pipelines/_index.md +++ b/content/en/continuous_integration/pipelines/_index.md @@ -145,13 +145,13 @@ If your CI provider is not supported, you can try setting up Pipeline Visibility | {{< ci-details title="Pipeline trace visualization" >}}Visualization of pipeline executions with associated tracing.{{< /ci-details >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | | {{< ci-details title="Job failure analysis" >}}Analysis and categorization of job failures using LLM models based on relevant logs. More info.{{< /ci-details >}} | | {{< X >}} | | | {{< X >}} | | | | | | | {{< ci-details title="Running pipelines" >}}Identification of pipelines executions that are running with associated tracing.{{< /ci-details >}} | {{< X >}} | {{< X >}} | | | {{< X >}} | | | | {{< X >}} | {{< X >}} | -| {{< ci-details title="Filter CI Jobs on the critical path" >}}Identification of CI jobs that are on the critical path of the pipeline.{{< /ci-details >}} | | {{< X >}} | | | | | | | | | +| {{< ci-details title="Filter CI Jobs on the critical path" >}}Identification of CI jobs that are on the critical path of the pipeline.{{< /ci-details >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | | {{< ci-details title="Partial retries" >}}Identification of partial retries (for example, when only a subset of jobs were retried).{{< /ci-details >}} | | {{< X >}} | | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | | {{< ci-details title="Step spans" >}}Step level spans are available for more granular visibility.{{< /ci-details >}} | {{< X >}} (_But are presented as job spans_) | | | | {{< X >}} | | {{< X >}} | | | {{< X >}} | | {{< ci-details title="Manual steps" >}}Identification of when there is a job with a manual approval phase in the overall pipeline.{{< /ci-details >}} | {{< X >}} | {{< X >}} | | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | | {{< X >}} | {{< X >}} | | {{< ci-details title="Approval wait time">}}Time for which a pipeline or job has been waiting for a manual approval.{{< /ci-details >}} | | {{< X >}} | | | {{< X >}} | {{< X >}} | | | {{< X >}} | | | {{< ci-details title="Queue time" >}}Time for which a pipeline or job was in the queue before execution.{{< /ci-details >}} | {{< X >}} | {{< X >}} | | {{< X >}} | {{< X >}} | | {{< X >}} | {{< X >}} | | {{< X >}} | -| {{< ci-details title="Execution time" >}}Time for which a pipeline has been actively running jobs.{{< /ci-details >}} | | {{< X >}} | | | | | | | | | +| {{< ci-details title="Execution time" >}}Time for which a pipeline has been actively running jobs.{{< /ci-details >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | | {{< ci-details title="Logs correlation" >}}Retrieval of pipeline or job logs from the CI provider. Logs are displayed on the Logs tab in the Pipeline Execution view.{{< /ci-details >}} | {{< X >}} | {{< X >}} | {{< X >}} | | {{< X >}} | {{< X >}} | | | {{< X >}} | | | {{< ci-details title="Infrastructure metric correlation" >}}Correlation of host-level information for the Datadog Agent, CI pipelines, or job runners to CI pipeline execution data.{{< /ci-details >}} | {{< X >}} | {{< X >}} | | {{< X >}} | {{< X >}} | | | | | | | {{< ci-details title="Custom spans for traced commands using datadog-ci" >}}Support for sending command-level events to CI Visibility to be incorporated into pipeline flame graph visualization. You can then query and analyze these events. {{< /ci-details >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | | | {{< X >}} | | diff --git a/content/en/continuous_integration/pipelines/awscodepipeline.md b/content/en/continuous_integration/pipelines/awscodepipeline.md index 8340f9d0e5e2f..def61717d610f 100644 --- a/content/en/continuous_integration/pipelines/awscodepipeline.md +++ b/content/en/continuous_integration/pipelines/awscodepipeline.md @@ -36,6 +36,8 @@ Set up tracing on AWS CodePipeline to collect data about pipeline executions, an | **Logs correlation | Logs correlation | Correlate pipeline and job spans to logs and enable [job log correlation](#collect-job-logs). | | [Approval wait time][17] | Approval wait time | View the amount of time jobs and pipelines wait for manual approvals. | | [Custom spans][18] | Custom spans | Configure custom spans for your pipelines. | +| [Filter CI Jobs on the critical path][19] | Filter CI Jobs on the critical path | Filter by jobs on the critical path. | +| [Execution time][20] | Execution time | View the amount of time pipelines have been running jobs. | *AWS CodePipeline running pipelines don't have Git information until they have finished.\ **AWS CodePipeline logs correlation is only available for AWS CodeBuild actions. @@ -160,3 +162,5 @@ The **CI Pipeline List** page shows data for only the default branch of each rep [16]: /logs/guide/send-aws-services-logs-with-the-datadog-lambda-function [17]: /glossary/#approval-wait-time [18]: /glossary/#custom-span +[19]: /continuous_integration/guides/identify_highest_impact_jobs_with_critical_path/ +[20]: /glossary/#pipeline-execution-time diff --git a/content/en/continuous_integration/pipelines/azure.md b/content/en/continuous_integration/pipelines/azure.md index c479722efa54d..8f139d6791f7b 100644 --- a/content/en/continuous_integration/pipelines/azure.md +++ b/content/en/continuous_integration/pipelines/azure.md @@ -34,6 +34,8 @@ Set up tracing on Azure Pipelines to gain real time insights into your CI/CD wor |---|---|---| | [Custom tags][10] [and measures at runtime][11] | Custom tags and measures at runtime | Configure [custom tags and measures][6] at runtime. | | [Custom spans][15] | Custom spans | Configure custom spans for your pipelines. | +| [Filter CI Jobs on the critical path][19] | Filter CI Jobs on the critical path | Filter by jobs on the critical path. | +| [Execution time][20] | Execution time | View the amount of time pipelines have been running jobs. | ## Configure the Datadog integration @@ -157,3 +159,5 @@ The **CI Pipeline List** page shows data for only the default branch of each rep [16]: /integrations/azure_devops/ [17]: /continuous_integration/search/#search-for-pipelines [18]: /logs/guide/best-practices-for-log-management/ +[19]: /continuous_integration/guides/identify_highest_impact_jobs_with_critical_path/ +[20]: /glossary/#pipeline-execution-time diff --git a/content/en/continuous_integration/pipelines/buildkite.md b/content/en/continuous_integration/pipelines/buildkite.md index 0553f95c30bac..b5a0a5bbaa94c 100644 --- a/content/en/continuous_integration/pipelines/buildkite.md +++ b/content/en/continuous_integration/pipelines/buildkite.md @@ -34,6 +34,8 @@ Set up tracing on Buildkite to optimize your resource usage, reduce overhead, an | [Queue time][13] | Queue time | View the amount of time pipeline jobs sit in the queue before processing. | | [Custom tags][10] [and measures at runtime][11] | Custom tags and measures at runtime | Configure [custom tags and measures][6] at runtime. | | [Custom spans][14] | Custom spans | Configure custom spans for your pipelines. | +| [Filter CI Jobs on the critical path][17] | Filter CI Jobs on the critical path | Filter by jobs on the critical path. | +| [Execution time][18] | Execution time | View the amount of time pipelines have been running jobs. | ## Configure the Datadog integration @@ -78,9 +80,9 @@ The resulting pipeline looks like the following: {{< img src="ci/buildkite-custom-tags.png" alt="Buildkite pipeline trace with custom tags" style="width:100%;">}} Any metadata with a key starting with `dd-measures.` and containing a numerical value will be set as -a metric tag that can be used to create numerical measures. +a metric tag that can be used to create numerical measures. -You can use the `buildkite-agent meta-data set` command to create these tags. +You can use the `buildkite-agent meta-data set` command to create these tags. For example, you can measure the binary size in a pipeline with this command: @@ -145,3 +147,5 @@ The **CI Pipeline List** page shows data for only the default branch of each rep [14]: /glossary/#custom-span [15]: /continuous_integration/explorer [16]: /continuous_integration/search/#search-for-pipelines +[17]: /continuous_integration/guides/identify_highest_impact_jobs_with_critical_path/ +[18]: /glossary/#pipeline-execution-time diff --git a/content/en/continuous_integration/pipelines/circleci.md b/content/en/continuous_integration/pipelines/circleci.md index b36079ba1d170..72f2e7db81ecd 100644 --- a/content/en/continuous_integration/pipelines/circleci.md +++ b/content/en/continuous_integration/pipelines/circleci.md @@ -36,6 +36,8 @@ Set up tracing on CircleCI to optimize the performance of your pipelines, improv | [Custom spans][13] | Custom spans | Configure custom spans for your pipelines. | | Custom pre-defined tags | Custom pre-defined tags | Set [custom tags][6] to all generated pipeline and job spans. | | [Custom tags][14] [and measures at runtime][15] | Custom tags and measures at runtime | Configure [custom tags and measures][7] at runtime. | +| [Filter CI Jobs on the critical path][18] | Filter CI Jobs on the critical path | Filter by jobs on the critical path. | +| [Execution time][19] | Execution time | View the amount of time pipelines have been running jobs. | ## Configure the Datadog integration @@ -128,3 +130,5 @@ The **CI Pipeline List** page shows data for only the default branch of each rep [15]: /glossary/#custom-measure [16]: /logs/guide/best-practices-for-log-management/ [17]: /continuous_integration/search/#search-for-pipelines +[18]: /continuous_integration/guides/identify_highest_impact_jobs_with_critical_path/ +[19]: /glossary/#pipeline-execution-time \ No newline at end of file diff --git a/content/en/continuous_integration/pipelines/codefresh.md b/content/en/continuous_integration/pipelines/codefresh.md index e8bb5aecd3d35..ebe68edbfcfcf 100644 --- a/content/en/continuous_integration/pipelines/codefresh.md +++ b/content/en/continuous_integration/pipelines/codefresh.md @@ -17,7 +17,7 @@ further_reading: ## Overview -[Codefresh][1] is a continuous integration and delivery platform built for Kubernetes which offers automation features that streamline the building, testing, and deploying of your applications. +[Codefresh][1] is a continuous integration and delivery platform built for Kubernetes which offers automation features that streamline the building, testing, and deploying of your applications. Set up tracing in Codefresh to collect data on each step of your pipelines, analyze performance bottlenecks, troubleshoot operational challenges, and monitor your deployment workflows. @@ -29,6 +29,8 @@ Set up tracing in Codefresh to collect data on each step of your pipelines, anal | [Manual steps][8] | Manual steps | View manually triggered pipelines. | | [Parameters][9] | Parameters | Set custom parameters (for example, [Codefresh variables][6]) when a pipeline is triggered. | | [Pipeline failure reasons][10] | Pipeline failure reasons | Identify pipeline failure reasons from error messages. | +| [Filter CI Jobs on the critical path][12] | Filter CI Jobs on the critical path | Filter by jobs on the critical path. | +| [Execution time][13] | Execution time | View the amount of time pipelines have been running jobs. | ## Configure the Datadog integration @@ -61,4 +63,6 @@ The **CI Pipeline List** page shows data for only the default branch of each rep [8]: /glossary/#manual-step [9]: /glossary/#parameter [10]: /glossary/#pipeline-failure -[11]: /continuous_integration/search/#search-for-pipelines \ No newline at end of file +[11]: /continuous_integration/search/#search-for-pipelines +[12]: /continuous_integration/guides/identify_highest_impact_jobs_with_critical_path/ +[13]: /glossary/#pipeline-execution-time diff --git a/content/en/continuous_integration/pipelines/custom.md b/content/en/continuous_integration/pipelines/custom.md index 2b33ea5ef8b5a..86deada25028c 100644 --- a/content/en/continuous_integration/pipelines/custom.md +++ b/content/en/continuous_integration/pipelines/custom.md @@ -34,6 +34,9 @@ You can send custom pipelines through HTTP using the [public API endpoint][1]. F | [Partial retries][10] | Partial pipelines | View partially retried pipeline executions. | | [Pipeline failure reasons][11] | Pipeline failure reasons | Identify pipeline failure reasons from error messages. | | [Queue time][12] | Queue time | View the amount of time pipeline jobs sit in the queue before processing. | +| [Filter CI Jobs on the critical path][16] | Filter CI Jobs on the critical path | Filter by jobs on the critical path. | +| [Execution time][17] | Execution time | View the amount of time pipelines have been running jobs. | + ## Configure CI Visibility @@ -128,3 +131,5 @@ The **CI Pipeline List** page shows data for only the default branch of each rep [13]: /continuous_integration/search/#search-for-pipelines [14]: https://app.datadoghq.com/organization-settings/api-keys [15]: /glossary/#running-pipeline +[16]: /continuous_integration/guides/identify_highest_impact_jobs_with_critical_path/ +[17]: /glossary/#pipeline-execution-time diff --git a/content/en/continuous_integration/pipelines/github.md b/content/en/continuous_integration/pipelines/github.md index 989c8fe3dead4..f96eea39e87bc 100644 --- a/content/en/continuous_integration/pipelines/github.md +++ b/content/en/continuous_integration/pipelines/github.md @@ -40,6 +40,8 @@ Set up CI Visibility in GitHub Actions to track the execution of your workflows, | [Queue time][8] | Queue time | View the amount of time pipeline jobs sit in the queue before processing. | | [Approval wait time][9] | Approval wait time | View the amount of time workflow runs and workflow jobs wait for manual approvals. | | [Custom spans][10] | Custom spans | Configure custom spans for your pipelines. | +| [Filter CI Jobs on the critical path][24] | Filter CI Jobs on the critical path | Filter by jobs on the critical path. | +| [Execution time][25] | Execution time | View the amount of time pipelines have been running jobs. | The following GitHub versions are supported: @@ -145,3 +147,5 @@ The **CI Pipeline List** page shows data for only the default branch of each rep [21]: https://github.com/actions/actions-runner-controller [22]: https://github.com/DataDog/datadog-agent/blob/main/pkg/config/config_template.yaml [23]: /continuous_integration/guides/use_ci_jobs_failure_analysis/ +[24]: /continuous_integration/guides/identify_highest_impact_jobs_with_critical_path/ +[25]: /glossary/#pipeline-execution-time diff --git a/content/en/continuous_integration/pipelines/gitlab.md b/content/en/continuous_integration/pipelines/gitlab.md index 5b8252b2fc0e5..5a299d5a7ddce 100644 --- a/content/en/continuous_integration/pipelines/gitlab.md +++ b/content/en/continuous_integration/pipelines/gitlab.md @@ -30,6 +30,7 @@ Set up tracing in GitLab to collect data on your pipeline executions, analyze pe |---|---|---| | [Running pipelines][24] | Running pipelines | View pipeline executions that are running. Queued or waiting pipelines show with status "Running" on Datadog. | | [CI jobs failure analysis][28] | CI jobs failure analysis | Analysis of the root causes of failed CI jobs based on relevant logs using LLM models. | +| [Filter CI Jobs on the critical path][29] | Filter CI Jobs on the critical path | Filter by jobs on the critical path. | | [Partial retries][19] | Partial pipelines | View partially retried pipeline executions. | | [Manual steps][20] | Manual steps | View manually triggered pipelines. | | [Queue time][21] | Queue time | View the amount of time pipeline jobs sit in the queue before processing. | @@ -449,4 +450,5 @@ The **CI Pipeline List** page shows data for only the default branch of each rep [25]: /glossary/#custom-span [26]: /continuous_integration/explorer [27]: /continuous_integration/search/#search-for-pipelines -[28]: /continuous_integration/guides/use_ci_jobs_failure_analysis/ \ No newline at end of file +[28]: /continuous_integration/guides/use_ci_jobs_failure_analysis/ +[29]: /continuous_integration/guides/identify_highest_impact_jobs_with_critical_path/ \ No newline at end of file diff --git a/content/en/continuous_integration/pipelines/jenkins.md b/content/en/continuous_integration/pipelines/jenkins.md index ff7caf62017cf..d0066eb1f29ed 100644 --- a/content/en/continuous_integration/pipelines/jenkins.md +++ b/content/en/continuous_integration/pipelines/jenkins.md @@ -38,6 +38,8 @@ Set up tracing in Jenkins to collect data across various stages of your pipeline | [Parameters][24] | Parameters | Set custom parameters (such as the default branch name or Git information) when a pipeline is triggered. | | [Pipeline failure reasons][25] | Pipeline failure reasons | Identify pipeline failure reasons from error messages. | | [Running pipelines][32] | Running pipelines | View pipeline executions that are running. Requires Jenkins plugin version >= 8.0.0 | +| [Filter CI Jobs on the critical path][33] | Filter CI Jobs on the critical path | Filter by jobs on the critical path. | +| [Execution time][34] | Execution time | View the amount of time pipelines have been running jobs. | The following Jenkins versions are supported: @@ -1256,3 +1258,5 @@ try restarting the Jenkins instance. [30]: /developers/dogstatsd/ [31]: /containers/docker/apm/#tracing-from-the-host [32]: /glossary/#running-pipeline +[33]: /continuous_integration/guides/identify_highest_impact_jobs_with_critical_path/ +[34]: /glossary/#pipeline-execution-time \ No newline at end of file diff --git a/content/en/continuous_integration/pipelines/teamcity.md b/content/en/continuous_integration/pipelines/teamcity.md index 3deb8261ae83c..90dc846dcefa9 100644 --- a/content/en/continuous_integration/pipelines/teamcity.md +++ b/content/en/continuous_integration/pipelines/teamcity.md @@ -28,6 +28,8 @@ Set up tracing in TeamCity to collect data about your pipeline executions, debug | [Partial retries][14] | Retry build triggers | View partially retried pipeline executions. | | [Queue time][15] | Queue time | View the amount of time pipeline jobs sit in the queue before processing. | | [Pipeline failure reasons][16] | Pipeline failure reasons | Identify pipeline failure reasons from error messages. | +| [Filter CI Jobs on the critical path][17] | Filter CI Jobs on the critical path | Filter by jobs on the critical path. | +| [Execution time][18] | Execution time | View the amount of time pipelines have been running jobs. | The following TeamCity versions are supported: @@ -41,12 +43,12 @@ To set up the integration: 1. Download the [Datadog CI Integration plugin][5] on the TeamCity server by going to **Administration** -> **Plugins** -> **Browse Plugin Repository**. -2. If you don't already have one, add a [TeamCity composite build][6] as the last build of the build chain. This build must have a dependency on the current last build of the chain and no other builds depending on it. +2. If you don't already have one, add a [TeamCity composite build][6] as the last build of the build chain. This build must have a dependency on the current last build of the chain and no other builds depending on it. Build chains that do not end with a composite build are ignored by the plugin. For example, consider an expected build chain where `Aggregating Results` is the last composite build: - + {{< img src="ci/teamcity_build_chain.png" alt="TeamCity build chain with composite build at the end" style="width:100%;">}} - + The final composite build must be properly configured in terms of version control settings, with the VCS Root attached and the [VCS Trigger][13] configured. 3. The following configuration parameters need to be present for TeamCity projects: @@ -55,8 +57,8 @@ To set up the integration: * **datadog.ci.site**: {{< region-param key="dd_site" code="true" >}} * **datadog.ci.enabled**: `true` (`false` can be used to disable the plugin for a specific project). - These configuration parameters should not have type **Password** to ensure the plugin can read their values correctly. You can add them to either TeamCity subprojects or the [TeamCity Root Project][10]. When added to the Root project, they are propagated to all its subprojects. For example, to enable the plugin for all projects, add `datadog.ci.enabled` with the value `true` to the Root Project. - + These configuration parameters should not have type **Password** to ensure the plugin can read their values correctly. You can add them to either TeamCity subprojects or the [TeamCity Root Project][10]. When added to the Root project, they are propagated to all its subprojects. For example, to enable the plugin for all projects, add `datadog.ci.enabled` with the value `true` to the Root Project. + For more information on defining configuration parameters, see the [TeamCity Project Hierarchy documentation][9]. 4. To enable the plugin, click on **Enable uploaded plugins** in the **Administration** -> **Plugins** page. @@ -67,7 +69,7 @@ Alternatively, restart the TeamCity server. ### Configure Git user information The plugin retrieves the Git author name and email based on the [TeamCity username style][7]. Datadog recommends using either **Author Name and Email** or **Author Email** username styles, as they -provide information about the user email. +provide information about the user email. When one of the other username styles is used (**UserId** or **Author Name**), the plugin automatically generates an email for the user by appending `@Teamcity` to the username. For example, if the **UserId** username style is used and the Git author username is `john.doe`, the plugin generates `john.doe@Teamcity` as the Git author email. The username style is defined for [VCS Roots][11], and can be modified in the VCS Root settings. @@ -109,3 +111,5 @@ Check these logs to get additional context on any issues with the plugin. [14]: /glossary/#partial-retry [15]: /glossary/#queue-time [16]: /glossary/#pipeline-failure +[17]: /continuous_integration/guides/identify_highest_impact_jobs_with_critical_path/ +[18]: /glossary/#pipeline-execution-time diff --git a/static/resources/json/civisibility-critical-path-gitlab-dashboard.json b/static/resources/json/civisibility-critical-path-dashboard.json similarity index 90% rename from static/resources/json/civisibility-critical-path-gitlab-dashboard.json rename to static/resources/json/civisibility-critical-path-dashboard.json index 999d3b39db3f0..19b1ca8c64c46 100644 --- a/static/resources/json/civisibility-critical-path-gitlab-dashboard.json +++ b/static/resources/json/civisibility-critical-path-dashboard.json @@ -59,7 +59,7 @@ }, "group_by": [], "search": { - "query": "ci_level:job @ci.on_critical_path:true $env $service $ci_provider $pipeline_name $job_name ci_partial_retry:false @duration:>0 $repository_id $git.branch -@ci.allowed_to_fail:true" + "query": "ci_level:job @ci.on_critical_path:true $env $service $ci_provider $pipeline_name $job_name @duration:>0 $repository_id $git.branch -@ci.allowed_to_fail:true" } } ], @@ -111,7 +111,7 @@ }, "group_by": [], "search": { - "query": "ci_level:job @ci.on_critical_path:true $env $service $ci_provider $pipeline_name $job_name @duration:>0 ci_partial_retry:false $repository_id $git.branch" + "query": "ci_level:job @ci.on_critical_path:true $env $service $ci_provider $pipeline_name $job_name @duration:>0 $repository_id $git.branch" } } } @@ -167,7 +167,7 @@ } ], "search": { - "query": "ci_level:job @ci.on_critical_path:true @ci.provider.name:gitlab ci_partial_retry:false @duration:>0 $env $service $ci_provider $pipeline_name $repository_id $job_name $git.branch" + "query": "ci_level:job @ci.on_critical_path:true @duration:>0 $env $service $ci_provider $pipeline_name $repository_id $job_name $git.branch" } }, { @@ -200,7 +200,7 @@ } ], "search": { - "query": "ci_level:job @ci.on_critical_path:true @ci.provider.name:gitlab ci_partial_retry:false @duration:>0 $env $service $ci_provider $pipeline_name $repository_id $job_name $git.branch" + "query": "ci_level:job @ci.on_critical_path:true @duration:>0 $env $service $ci_provider $pipeline_name $repository_id $job_name $git.branch" } }, { @@ -233,7 +233,7 @@ } ], "search": { - "query": "ci_level:job @ci.provider.name:gitlab ci_partial_retry:false @duration:>0 $env $service $ci_provider $pipeline_name $repository_id $job_name $git.branch" + "query": "ci_level:job @duration:>0 $env $service $ci_provider $pipeline_name $repository_id $job_name $git.branch" } } ], @@ -330,7 +330,7 @@ } ], "search": { - "query": "ci_level:job @ci.on_critical_path:true @ci.provider.name:gitlab ci_partial_retry:false @duration:>0 $env $service $ci_provider $pipeline_name $repository_id $job_name $git.branch" + "query": "ci_level:job @ci.on_critical_path:true @duration:>0 $env $service $ci_provider $pipeline_name $repository_id $job_name $git.branch" } }, { @@ -363,7 +363,7 @@ } ], "search": { - "query": "ci_level:job @ci.on_critical_path:true @ci.provider.name:gitlab ci_partial_retry:false @duration:>0 $env $service $ci_provider $pipeline_name $repository_id $job_name $git.branch" + "query": "ci_level:job @ci.on_critical_path:true @duration:>0 $env $service $ci_provider $pipeline_name $repository_id $job_name $git.branch" } }, { @@ -396,7 +396,7 @@ } ], "search": { - "query": "ci_level:job @ci.provider.name:gitlab ci_partial_retry:false @duration:>0 $env $service $ci_provider $pipeline_name $repository_id $job_name $git.branch @ci.critical_path.parallelized:true" + "query": "ci_level:job @duration:>0 $env $service $ci_provider $pipeline_name $repository_id $job_name $git.branch @ci.critical_path.parallelized:true" } } ], @@ -478,7 +478,7 @@ } ], "search": { - "query": "ci_level:job @ci.on_critical_path:true $env $service $ci_provider $pipeline_name $job_name ci_partial_retry:false $repository_id $git.branch" + "query": "ci_level:job @ci.on_critical_path:true $env $service $ci_provider $pipeline_name $job_name $repository_id $git.branch" } } ] @@ -548,72 +548,6 @@ ], "layout_type": "ordered", "notify_list": [], - "template_variable_presets": [ - { - "name": "GitLab", - "template_variables": [ - { - "name": "ci_provider", - "value": "gitlab" - } - ] - }, - { - "name": "GitLab - dd-go", - "template_variables": [ - { - "name": "repository_id", - "value": "gitlab.ddbuild.io/DataDog/dd-go" - }, - { - "name": "ci_provider", - "value": "gitlab" - } - ] - }, - { - "name": "GitLab - dd-go - tests", - "template_variables": [ - { - "name": "repository_id", - "value": "gitlab.ddbuild.io/DataDog/dd-go" - }, - { - "name": "ci_provider", - "value": "gitlab" - }, - { - "name": "job_name", - "value": "*test*" - } - ] - }, - { - "name": "GitLab - logs-backend", - "template_variables": [ - { - "name": "repository_id", - "value": "gitlab.ddbuild.io/DataDog/logs-backend" - }, - { - "name": "ci_provider", - "value": "gitlab" - } - ] - }, - { - "name": "GitLab - web-ui", - "template_variables": [ - { - "name": "repository_id", - "value": "gitlab.ddbuild.io/DataDog/web-ui" - }, - { - "name": "ci_provider", - "value": "gitlab" - } - ] - } - ], + "template_variable_presets": [], "reflow_type": "fixed" } \ No newline at end of file