[SDCI-1909] Add job failure analysis for Azure Pipelines #33039
Conversation
| | [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. | |
There was a problem hiding this comment.
For other providers (GitHub and GitLab), we have Logs Correlation and Job Failure analysis as "features".
I think we either:
- do not display Job Failure analysis here (since logs correlation is in preview),
- or we go ahead and add Logs Correlation as another feature here (even if in preview).
There was a problem hiding this comment.
I would add both in the table with "(Preview)" next to them. To let the customer know that those features are available just that they have to request access. But if the standard is to not show there anything that is not fully release I would remove it.
There was a problem hiding this comment.
At the end, I will remove it from the table.
maycmlee
left a comment
maycmlee
left a comment
There was a problem hiding this comment.
Some suggestions and an issue with indentation
| |---|---|---| | ||
| | Pipeline Visibility | Platform | Definition | | ||
| |-------------------------------------------------|---|---| | ||
| | [CI jobs failure analysis][21] | CI jobs failure analysis | Analysis of the root causes of failed CI jobs based on relevant logs using LLM models. | |
There was a problem hiding this comment.
| | [CI jobs failure analysis][21] | CI jobs failure analysis | Analysis of the root causes of failed CI jobs based on relevant logs using LLM models. | | |
| | [CI jobs failure analysis][21] | CI jobs failure analysis | Uses LLM models on relevant logs to analyze the root cause of failed CI jobs. | |
| |---|:---:|:---:|:---:|:---:|:---:|:---:|:---:|:---:|:---:|:---:| | ||
| | {{< 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" >}}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 >}} | {{< X >}} | | | | | |
There was a problem hiding this comment.
| | {{< 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 >}} | {{< 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 >}} | | | | | |
| a. Navigate to **Organization settings** in your DevOps console. | ||
| b. Click **Users** from the left side panel, then click on **Add Users**. | ||
| 2. Add the Datadog app registration to your Azure DevOps organization: | ||
| a. Navigate to **Organization settings** in your DevOps console. |
There was a problem hiding this comment.
The sub-steps indentation isn't showing up in the preview. Let me know if you need help with this.
|
Hi @maycmlee! Thanks for your suggestions. I have applied them to Azure and to the other CI Providers pages in which we had the same text. |
maycmlee
left a comment
maycmlee
left a comment
There was a problem hiding this comment.
Thanks @borja-gomez! Sorry just a couple of suggestions I missed. Also, the indentation is still not working. Is it okay if I make a commit to see if I can fix it?
Co-authored-by: May Lee <may.lee@datadoghq.com>
Co-authored-by: May Lee <may.lee@datadoghq.com>
# Conflicts: # content/en/continuous_integration/pipelines/github.md # content/en/continuous_integration/pipelines/gitlab.md
borja-gomez
force-pushed
the
borja.gomez/SDCI-1909/job-failure-analysis-for-azure
branch
from
06210f9 to
a4f1fde
Compare
maycmlee
left a comment
maycmlee
left a comment
There was a problem hiding this comment.
Looks good! Fixed the indentation problem. Feel free to merge if it's ready.
What does this PR do? What is the motivation?
In CI Visibility we now support CI jobs failure analysis for Azure Pipelines.
This PR adds Azure Pipelines to the supported providers for that feature and explains this feature in the provider specific documentation.
Merge instructions
Merge readiness:
For Datadog employees:
Your branch name MUST follow the
<name>/<description>convention and include the forward slash (/). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.
Additional notes