CI Visibility setup - revamp [DOCS-11713]

config/_default/menus/main.en.yaml

@@ -5017,7 +5017,7 @@ menu:
       parent: pipeline_visibility
       identifier: ci_awscodepipeline
       weight: 101
-    - name: Azure
+    - name: Azure Pipelines
       url: continuous_integration/pipelines/azure/
       parent: pipeline_visibility
       identifier: ci_azure

content/en/continuous_integration/pipelines/_index.md

@@ -22,11 +22,11 @@ cascade:
 
 ## Overview
 
-[Pipeline Visibility][1] provides a pipeline-first view into your CI health by displaying important metrics and results from your pipelines. It helps you troubleshoot pipeline failures, address performance bottlenecks, and track CI performance and reliability over time.
+[CI Visibility][1] provides a pipeline-first view into your CI health by displaying important metrics and results from your pipelines. It helps you troubleshoot pipeline failures, address performance bottlenecks, and track CI performance and reliability over time.
 
 ## Setup
 
-{{< whatsnext desc="Select your CI provider to set up Pipeline Visibility in Datadog:" >}}
+{{< whatsnext desc="Select your CI provider to set up CI Visibility in Datadog:" >}}
     {{< nextlink href="continuous_integration/pipelines/awscodepipeline" >}}AWS CodePipeline{{< /nextlink >}}
     {{< nextlink href="continuous_integration/pipelines/azure" >}}Azure{{< /nextlink >}}
     {{< nextlink href="continuous_integration/pipelines/buildkite" >}}Buildkite{{< /nextlink >}}
@@ -41,98 +41,7 @@ cascade:
     {{< nextlink href="continuous_integration/pipelines/custom_tags_and_measures" >}}Custom Tags and Measures{{< /nextlink >}}
 {{< /whatsnext >}}
 
-### Terminology
-
-While the concept of a CI pipeline may vary depending on your provider, see how those concepts correspond to the definition of a CI pipeline in Datadog Pipeline Visibility:
-
-{{< tabs >}}
-{{% tab "GitHub Actions" %}}
-
-| Datadog  | GitHub Actions |
-|----------|----------------|
-| Pipeline | Workflow       |
-| Job      | Job            |
-| Step     | Step           |
-
-{{% /tab %}}
-{{% tab "GitLab" %}}
-
-| Datadog                    | GitLab   |
-|----------------------------|----------|
-| Pipeline                   | Pipeline |
-| Stage                      | Stage    |
-| Job                        | Job      |
-| _Not available in Datadog_ | Script   |
-
-{{% /tab %}}
-{{% tab "Jenkins" %}}
-
-| Datadog  | Jenkins  |
-|----------|----------|
-| Pipeline | Pipeline |
-| Stage    | Stage    |
-| Job      | Step     |
-
-{{% /tab %}}
-{{% tab "CircleCI" %}}
-
-| Datadog                    | CircleCI  |
-|----------------------------|-----------|
-| Pipeline                   | Workflow  |
-| Job                        | Job       |
-| _Not available in Datadog_ | Step      |
-
-{{% /tab %}}
-{{% tab "Buildkite" %}}
-
-| Datadog                    | Buildkite                       |
-|----------------------------|---------------------------------|
-| Pipeline                   | Build (execution of a pipeline) |
-| Job                        | Job (execution of a step)       |
-
-{{% /tab %}}
-{{% tab "TeamCity" %}}
-
-| Datadog                    | TeamCity    |
-|----------------------------|-------------|
-| Pipeline                   | Build Chain |
-| Job                        | Build       |
-| _Not available in Datadog_ | Step        |
-
-{{% /tab %}}
-{{% tab "Azure Pipelines" %}}
-
-| Datadog                    | Azure Pipelines |
-|----------------------------|-----------------|
-| Pipeline                   | Pipeline        |
-| Stage                      | Stage           |
-| Job                        | Job             |
-| _Not available in Datadog_ | Step            |
-
-{{% /tab %}}
-{{% tab "AWS CodePipeline" %}}
-
-| Datadog  | AWS CodePipeline |
-|----------|------------------|
-| Pipeline | Pipeline         |
-| Stage    | Stage            |
-| Job      | Action           |
-
-{{% /tab %}}
-
-{{% tab "Other CI Providers" %}}
-
-| Datadog  | Other CI Providers |
-|----------|--------------------|
-| Pipeline | Pipeline           |
-| Stage    | Stage              |
-| Job      | Job                |
-| Step     | Step               |
-
-{{% /tab %}}
-{{< /tabs >}}
-
-If your CI provider is not supported, you can try setting up Pipeline Visibility through the [public API endpoint][2].
+If your CI provider is not supported, you can try setting up CI Visibility through the [public API endpoint][2].
 
 ### Supported features
 

content/en/continuous_integration/pipelines/awscodepipeline.md

@@ -1,5 +1,5 @@
 ---
-title: Set up Tracing on a AWS CodePipeline Pipeline
+title: AWS CodePipeline Setup for CI Visibility
 aliases:
   - /continuous_integration/setup_pipelines/codepipeline
 further_reading:
@@ -21,7 +21,7 @@ further_reading:
 
 [AWS CodePipeline][1] is a fully managed continuous delivery service that helps you automate your release pipelines for fast and reliable application and infrastructure updates.
 
-Set up tracing on AWS CodePipeline to collect data about pipeline executions, analyze performance bottlenecks or operational issues, and monitor your deployment workflows.
+Set up CI Visibility for AWS CodePipeline to collect data about pipeline executions, analyze performance bottlenecks or operational issues, and monitor your deployment workflows.
 
 ### Compatibility
 
@@ -38,6 +38,16 @@ Set up tracing on AWS CodePipeline to collect data about pipeline executions, an
 *AWS CodePipeline running pipelines don't have Git information until they have finished.\
 **AWS CodePipeline logs correlation is only available for AWS CodeBuild actions.
 
+### Terminology
+
+This table shows the mapping of concepts between Datadog CI Visibility and AWS CodePipeline:
+
+| Datadog  | AWS CodePipeline |
+|----------|------------------|
+| Pipeline | Pipeline         |
+| Stage    | Stage            |
+| Job      | Action           |
+
 ## Configure the Datadog integration
 
 To set up the integration between [AWS CodePipeline][1] and Pipeline Visibility, create two AWS resources.

content/en/continuous_integration/pipelines/azure.md

@@ -1,5 +1,5 @@
 ---
-title: Set up Tracing on an Azure Pipeline
+title: Azure Pipelines Setup for CI Visibility
 aliases:
   - /continuous_integration/setup_pipelines/azure
 further_reading:
@@ -22,7 +22,7 @@ Azure DevOps Server is not officially supported.
 
 [Azure Pipelines][1] is a continuous integration and delivery service that supports any language, platform, or cloud.
 
-Set up tracing on Azure Pipelines to gain real time insights into your CI/CD workflows, track pipeline performance, analyze inefficiencies, and manage your deployment operations.
+Set up CI Visibility for Azure Pipelines to gain real time insights into your CI/CD workflows, track pipeline performance, analyze inefficiencies, and manage your deployment operations.
 
 ### Compatibility
 
@@ -33,6 +33,17 @@ Set up tracing on Azure Pipelines to gain real time insights into your CI/CD wor
 | [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. |
 
+### Terminology
+
+This table shows the mapping of concepts between Datadog CI Visibility and Azure Pipelines:
+
+| Datadog                    | Azure Pipelines |
+|----------------------------|-----------------|
+| Pipeline                   | Pipeline        |
+| Stage                      | Stage           |
+| Job                        | Job             |
+| _Not available in Datadog_ | Step            |
+
 ## Configure the Datadog integration
 
 The Datadog integration for [Azure Pipelines][16] works by using [service hooks][2] to send data to Datadog.

content/en/continuous_integration/pipelines/buildkite.md

@@ -1,5 +1,5 @@
 ---
-title: Set up Tracing on a Buildkite Pipeline
+title: Buildkite Setup for CI Visibility
 aliases:
   - /continuous_integration/setup_pipelines/buildkite
 further_reading:
@@ -18,7 +18,7 @@ further_reading:
 
 [Buildkite][1] is a continuous integration and deployment platform that allows you to run builds on your own infrastructure, providing you with full control over security and customizing your build environment while managing orchestration in the cloud.
 
-Set up tracing on Buildkite to optimize your resource usage, reduce overhead, and improve the speed and quality of your software development lifecycle.
+Set up CI Visibility for Buildkite to optimize your resource usage, reduce overhead, and improve the speed and quality of your software development lifecycle.
 
 ### Compatibility
 
@@ -33,6 +33,15 @@ Set up tracing on Buildkite to optimize your resource usage, reduce overhead, an
 | [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. |
 
+### Terminology
+
+This table shows the mapping of concepts between Datadog CI Visibility and Buildkite:
+
+| Datadog                    | Buildkite                       |
+|----------------------------|---------------------------------|
+| Pipeline                   | Build (execution of a pipeline) |
+| Job                        | Job (execution of a step)       |
+
 ## Configure the Datadog integration
 
 To set up the Datadog integration for [Buildkite][1]:

content/en/continuous_integration/pipelines/circleci.md

@@ -1,5 +1,5 @@
 ---
-title: Set up Tracing on a CircleCI Workflow
+title: CircleCI Setup for CI Visibility
 aliases:
   - /continuous_integration/setup_pipelines/circleci
 further_reading:
@@ -21,7 +21,7 @@ further_reading:
 
 [CircleCI][1] is a continuous integration and delivery platform that enables teams to build, test, and deploy software at scale.
 
-Set up tracing on CircleCI to optimize the performance of your pipelines, improve collaboration across teams, and ensure consistent, compliant build processes.
+Set up CI Visibility for CircleCI to optimize the performance of your pipelines, improve collaboration across teams, and ensure consistent, compliant build processes.
 
 ### Compatibility
 
@@ -35,6 +35,16 @@ Set up tracing on CircleCI to optimize the performance of your pipelines, improv
 | [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. |
 
+### Terminology
+
+This table shows the mapping of concepts between Datadog CI Visibility and CircleCI:
+
+| Datadog                    | CircleCI  |
+|----------------------------|-----------|
+| Pipeline                   | Workflow  |
+| Job                        | Job       |
+| _Not available in Datadog_ | Step      |
+
 ## Configure the Datadog integration
 
 The Datadog integration for [CircleCI][1] works by using [webhooks][2] to send data to Datadog.

content/en/continuous_integration/pipelines/codefresh.md

@@ -1,5 +1,5 @@
 ---
-title: Set up Tracing on Codefresh Pipelines
+title: Codefresh Setup for CI Visibility
 aliases:
   - /continuous_integration/setup_pipelines/codefresh
 further_reading:
@@ -15,7 +15,7 @@ further_reading:
 
 [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.
+Set up CI Visibility for Codefresh to collect data on each step of your pipelines, analyze performance bottlenecks, troubleshoot operational challenges, and monitor your deployment workflows.
 
 ### Compatibility
 

content/en/continuous_integration/pipelines/github.md

@@ -1,5 +1,5 @@
 ---
-title: Set up CI Visibility on GitHub Actions Workflows
+title: GitHub Actions Setup for CI Visibility
 aliases:
   - /continuous_integration/setup_pipelines/github
 further_reading:
@@ -21,7 +21,7 @@ further_reading:
 
 [GitHub Actions][1] is an automation tool that allows you to build, test, and deploy your code in GitHub. Create workflows that automate every step of your development process, streamlining software updates and enhancing code quality with CI/CD features integrated into your repositories.
 
-Set up CI Visibility in GitHub Actions to track the execution of your workflows, identify performance bottlenecks, troubleshoot operational issues, and optimize your deployment processes.
+Set up CI Visibility for GitHub Actions to track the execution of your workflows, identify performance bottlenecks, troubleshoot operational issues, and optimize your deployment processes.
 
 ### Compatibility
 
@@ -45,6 +45,16 @@ The following GitHub versions are supported:
 - GitHub.com (SaaS)
 - GitHub Enterprise Server (GHES) 3.5.0 or later
 
+### Terminology
+
+This table shows the mapping of concepts between Datadog CI Visibility and GitHub Actions:
+
+| Datadog  | GitHub Actions |
+|----------|----------------|
+| Pipeline | Workflow       |
+| Job      | Job            |
+| Step     | Step           |
+
 ## Configure the Datadog integration
 
 ### Configure a GitHub App

content/en/continuous_integration/pipelines/gitlab.md

@@ -1,5 +1,5 @@
 ---
-title: Set up Tracing on a GitLab Pipeline
+title: GitLab Setup for CI Visibility
 aliases:
   - /continuous_integration/setup_pipelines/gitlab
 further_reading:
@@ -18,7 +18,7 @@ further_reading:
 
 [GitLab][18] is a DevOps platform that automates the software development lifecycle with integrated CI/CD features, enabling automated, continuous deployment of applications with built-in security controls.
 
-Set up tracing in GitLab to collect data on your pipeline executions, analyze performance bottlenecks, troubleshoot operational issues, and optimize your deployment workflows.
+Set up CI Visibility for GitLab to collect data on your pipeline executions, analyze performance bottlenecks, troubleshoot operational issues, and optimize your deployment workflows.
 
 ### Compatibility
 
@@ -46,6 +46,17 @@ The following GitLab versions are supported:
 - GitLab >= 14.1 (self-hosted)
 - GitLab >= 13.7.0 (self-hosted) with the `datadog_ci_integration` feature flag enabled
 
+### Terminology
+
+This table shows the mapping of concepts between Datadog CI Visibility and GitLab:
+
+| Datadog                    | GitLab   |
+|----------------------------|----------|
+| Pipeline                   | Pipeline |
+| Stage                      | Stage    |
+| Job                        | Job      |
+| _Not available in Datadog_ | Script   |
+
 ## Configure the Datadog integration
 
 {{< tabs >}}

content/en/continuous_integration/pipelines/jenkins.md

@@ -1,5 +1,5 @@
 ---
-title: Set up Tracing on a Jenkins Pipeline
+title: Jenkins Setup for CI Visibility
 aliases:
   - /continuous_integration/setup_pipelines/jenkins
 further_reading:
@@ -18,7 +18,7 @@ further_reading:
 
 [Jenkins][19] is an automation server with continuous integration and delivery features. With its plugin architecture, Jenkins can be customized to fit any CI/CD need and automates all aspects of project development, testing, and deployment.
 
-Set up tracing in Jenkins to collect data across various stages of your pipeline executions, identify performance bottlenecks, resolve operational challenges, and refine your deployment processes.
+Set up CI Visibility for Jenkins to collect data across various stages of your pipeline executions, identify performance bottlenecks, resolve operational challenges, and refine your deployment processes.
 
 ### Compatibility
 
@@ -44,6 +44,16 @@ The following Jenkins versions are supported:
 This integration supports both Agentless and Agent-based installation.
 Installing the Agent is required for infrastructure metrics correlation.
 
+### Terminology
+
+This table shows the mapping of concepts between Datadog CI Visibility and Jenkins:
+
+| Datadog  | Jenkins  |
+|----------|----------|
+| Pipeline | Pipeline |
+| Stage    | Stage    |
+| Job      | Step     |
+
 ## Install the Datadog Agent
 
 Skip this step if you do not need infrastructure metrics correlation.