[SDCI-1909] Add job failure analysis for Azure Pipelines

content/en/continuous_integration/guides/use_ci_jobs_failure_analysis.md

@@ -94,6 +94,7 @@ CI jobs failure analysis is available for the following CI providers:
 
 * [GitHub Actions][1]
 * [GitLab][2]
+* [Azure Pipeline][8]
 
 **Note:** You must enable CI job logs collection, and the logs need to be indexed. To set up CI job logs collection, select your CI provider on [Pipeline Visibility][6] and follow the instructions to collect job logs.
 
@@ -147,3 +148,4 @@ For PR Comments to be posted, your repositories need to be integrated with Datad
 [5]:/dashboards/
 [6]:/continuous_integration/pipelines/#setup
 [7]:/integrations/guide/source-code-integration/#connect-your-git-repositories-to-datadog
+[8]:/continuous_integration/pipelines/azure/

content/en/continuous_integration/pipelines/_index.md

@@ -139,7 +139,7 @@ If your CI provider is not supported, you can try setting up Pipeline Visibility
 |  | Jenkins | GitLab | CircleCI | Buildkite | GitHub Actions | Azure Pipelines | Codefresh | TeamCity | AWS CodePipeline | Other CI Providers |
 |---|:---:|:---:|:---:|:---:|:---:|:---:|:---:|:---:|:---:|:---:|
 | {{< 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. <a href="https://docs.datadoghq.com/continuous_integration/guides/use_ci_jobs_failure_analysis/">More info</a>.{{< /ci-details >}} | | {{< X >}} |  |  | {{< X >}} |  |  |  |  |  |
+| {{< ci-details title="Job failure analysis" >}}Uses LLM models on relevant logs to analyze and categorize job failures. <a href="https://docs.datadoghq.com/continuous_integration/guides/use_ci_jobs_failure_analysis/">More info</a>.{{< /ci-details >}} | | {{< X >}} |  |  | {{< 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="Critical path analysis" >}}Identification of CI jobs that are on the critical path of the pipeline. <a href="https://docs.datadoghq.com/continuous_integration/guides/identify_highest_impact_jobs_with_critical_path/">More info</a>{{< /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 >}} |
@@ -176,4 +176,4 @@ You can export your search query to a [CI Pipeline monitor][12] on the [**Execut
 [11]: /notebooks
 [12]: /monitors/types/ci
 [13]: https://app.datadoghq.com/ci/test-runs
-[14]: /continuous_integration/guides/use_ci_jobs_failure_analysis/
+[14]: /continuous_integration/guides/use_ci_jobs_failure_analysis/

content/en/continuous_integration/pipelines/azure.md

@@ -26,12 +26,12 @@ Set up tracing on Azure Pipelines to gain real time insights into your CI/CD wor
 
 ### Compatibility
 
-| Pipeline Visibility | Platform | Definition |
-|---|---|---|
-| [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. |
+| Pipeline Visibility                             | Platform                            | Definition                                                |
+|-------------------------------------------------|-------------------------------------|-----------------------------------------------------------|
+| [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
 
@@ -119,15 +119,22 @@ To enable job log collection:
 
 1. Install a Datadog app registration on your Azure console. Follow the steps in the [Azure integration tile][14].
 
-2. Add the Datadog app registration to your Azure DevOps organization:  
-  a. Navigate to **Organization settings** in your DevOps console.  
-  b. Click **Users** from the left side panel, then click on **Add Users**.  
-  **Note**: If you don't see the **Add Users** button, you may not have the necessary permissions.
+2. Add the Datadog app registration to your Azure DevOps organization:
+  <br>a. Navigate to **Organization settings** in your DevOps console.
+  <br>b. Click **Users** from the left side panel, then click **Add Users**.<br>**Note**: If you don't see the **Add Users** button, you may not have the necessary permissions.
 
 To enable log collection, add your app registration as a user with Basic Access Level to each project. Alternatively, you can click  **Add to all projects** to configure all projects in bulk.
 
 Logs are billed separately from CI Visibility. Log retention, exclusion, and indexes are configured in [Log Management][18]. Logs for Azure jobs can be identified by the `datadog.product:cipipeline` and `source:azurepipelines` tags.
 
+### CI jobs failure analysis
+
+If job logs collection is enabled, CI Visibility uses LLM models to compute the analysis for failed CI jobs based on relevant logs coming from Azure Pipelines.
+
+You can also add job failure analysis to a PR comment. See the guide on [using PR comments][22].
+
+For a full explanation, see the guide on [using CI jobs failure analysis][21].
+
 ## Visualize pipeline data in Datadog
 
 The [**CI Pipeline List**][4] and [**Executions**][5] pages populate with data after the workflows finish.
@@ -157,3 +164,5 @@ The **CI Pipeline List** page shows data for only the default branch of each rep
 [18]: /logs/guide/best-practices-for-log-management/
 [19]: /continuous_integration/guides/identify_highest_impact_jobs_with_critical_path/
 [20]: /glossary/#pipeline-execution-time
+[21]: /continuous_integration/guides/use_ci_jobs_failure_analysis/
+[22]: /continuous_integration/guides/use_ci_jobs_failure_analysis/#using-pr-comments

content/en/continuous_integration/pipelines/github.md

@@ -28,7 +28,7 @@ Set up CI Visibility in GitHub Actions to track the execution of your workflows,
 | Pipeline Visibility | Platform | Definition |
 |---|---|---|
 | [Running pipelines][2] | Running pipelines | View pipeline executions that are running. Queued or waiting pipelines show with status "Running" on Datadog. |
-| [CI jobs failure analysis][23] | CI jobs failure analysis | Analysis of the root causes of failed CI jobs based on relevant logs using LLM models. |
+| [CI jobs failure analysis][23] | CI jobs failure analysis | Uses LLM models on relevant logs to analyze the root cause of failed CI jobs. |
 | [Partial retries][3] | Partial pipelines | View partially retried pipeline executions. |
 | Logs correlation | Logs correlation | Correlate pipeline and job spans to logs and enable [job log collection](#collect-job-logs). |
 | Infrastructure metric correlation | Infrastructure metric correlation | Correlate jobs to [infrastructure host metrics][4] for GitHub jobs. |
@@ -106,7 +106,7 @@ To see the metrics, click on a job span in the trace view. A window opens with a
 
 ### CI jobs failure analysis
 
-If job logs collection is enabled, CI Visibility computes analysis using LLM models for failed CI jobs based on relevant logs coming from GitHub Actions.
+If job logs collection is enabled, CI Visibility uses LLM models to analyze failed CI jobs based on relevant logs coming from GitHub Actions.
 
 You can also add job failure analysis to a PR comment. See the guide on [using PR comments][26].
 

content/en/continuous_integration/pipelines/gitlab.md

@@ -25,7 +25,7 @@ Set up tracing in GitLab to collect data on your pipeline executions, analyze pe
 | Pipeline Visibility | Platform | Definition |
 |---|---|---|
 | [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. |
+| [CI jobs failure analysis][28] | CI jobs failure analysis | Uses LLM models on relevant logs to analyze the root cause of failed CI jobs. |
 | [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. |
@@ -303,7 +303,7 @@ For failed GitLab pipeline executions, each error under the `Errors` tab within
 
 #### CI jobs failure analysis
 
-If job logs collection is enabled, CI Visibility computes analysis using LLM models for failed CI jobs based on relevant logs coming from GitLab.
+If job logs collection is enabled, CI Visibility uses LLM models to analyze failed CI jobs based on relevant logs coming from GitLab.
 
 You can also add job failure analysis to a PR comment. See the guide on [using PR comments][30].