[SDCI-2062] Update Azure pipelines docs to show GA of log collection #34122
+12
−11
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Preview links (active after the
|
Signed-off-by: Borja Gomez <borja.gomez@datadoghq.com>
Signed-off-by: Borja Gomez <borja.gomez@datadoghq.com>
borja-gomez
force-pushed
the
borja.gomez/SDCI-2062/azure-logs-ga
branch
from
746509d to
8ead3bb
Compare
domalessi
reviewed
Jan 27, 2026
Contributor
domalessi
left a comment
domalessi
left a comment
There was a problem hiding this comment.
Left a few suggestions to tighten up and align with Datadog docs style. Let me know if you have any questions, and hit me up for re-review when ready!
|
|
||
| | Pipeline Visibility | Platform | Definition | | ||
| |-------------------------------------------------|-------------------------------------|-----------------------------------------------------------| | ||
| | [CI jobs failure analysis][21] | CI jobs failure analysis | Uses LLM models on relevant logs to analyze the root cause of failed CI jobs. | |
Contributor
There was a problem hiding this comment.
For consistency with the others.
Suggested change
| | [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 jobs failure analysis][21] | CI jobs failure analysis | Use LLM models on relevant logs to analyze the root cause of failed CI jobs. | |
| | Pipeline Visibility | Platform | Definition | | ||
| |-------------------------------------------------|-------------------------------------|-----------------------------------------------------------| | ||
| | [CI jobs failure analysis][21] | CI jobs failure analysis | Uses LLM models on relevant logs to analyze the root cause of failed CI jobs. | | ||
| | Logs correlation | Logs correlation | Correlate pipeline and job spans to logs and enable [job log collection](#collect-job-logs). | |
Contributor
There was a problem hiding this comment.
This line reads a bit like a mix of definition + setup. Does this maintain your intention?
Suggested change
| | Logs correlation | Logs correlation | Correlate pipeline and job spans to logs and enable [job log collection](#collect-job-logs). | | |
| | Logs correlation | Logs correlation | Correlate pipeline and job spans with logs. Requires [job log collection](#collect-job-logs). | |
|
|
||
| Pipelines appear in Datadog immediately after CI Visibility is enabled for an organization or project. | ||
|
|
||
| <div class="alert alert-danger">If you previously configured Azure Pipelines using Service Hook Subscriptions, disable that integration before enabling CI Visibility for the same projects to avoid duplicate pipeline events. Running both integrations simultaneously does not incur additional costs, but creates duplicate data.</div> |
Contributor
There was a problem hiding this comment.
Breaking up/tightening up a bit for clarity
Suggested change
| <div class="alert alert-danger">If you previously configured Azure Pipelines using Service Hook Subscriptions, disable that integration before enabling CI Visibility for the same projects to avoid duplicate pipeline events. Running both integrations simultaneously does not incur additional costs, but creates duplicate data.</div> | |
| <div class="alert alert-danger">If you previously configured Azure Pipelines using Service Hook Subscriptions, disable that integration before enabling CI Visibility for the same projects. Running both integrations simultaneously does not incur additional costs, but it creates duplicate data.</div> |
| To enable job log collection: | ||
|
|
||
| 1. Install a Datadog app registration on your Azure console. Follow the steps in the [Azure integration tile][14]. | ||
| Azure log pulling will only be enabled if you have set up the Datadog integration, which is the preferred way. To enable job log collection: |
Contributor
There was a problem hiding this comment.
Suggested change
| Azure log pulling will only be enabled if you have set up the Datadog integration, which is the preferred way. To enable job log collection: |
|
|
||
| <div class="alert alert-info">Azure Log Collection is in Preview. To request access, fill out <a href="https://forms.gle/vXEQQcPLARdSDLd27">this form</a>.</div> | ||
|
|
||
| Datadog supports log collection for your Azure DevOps pipelines. |
Contributor
There was a problem hiding this comment.
Suggested change
| Datadog supports log collection for your Azure DevOps pipelines. | |
| Datadog supports log collection for Azure DevOps pipelines. Log collection is enabled only after you set up the Datadog Azure DevOps integration. | |
| To enable job log collection: |
| 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. | ||
| 1. Set up the Datadog integration for Azure DevOps. Follow the steps in the [Azure integration tile][14]. |
Contributor
There was a problem hiding this comment.
Suggested change
| 1. Set up the Datadog integration for Azure DevOps. Follow the steps in the [Azure integration tile][14]. | |
| 1. Set up the Datadog Azure DevOps integration by following the steps in the [Azure integration tile][14]. |
Comment on lines
+169
to
+171
| 2. Enable log pulling in the Datadog UI: | ||
| <br>a. Navigate to [CI Visibility Settings][23] in your Datadog account. | ||
| <br>b. Enable log pulling for Azure DevOps. |
Contributor
There was a problem hiding this comment.
Suggested change
| 2. Enable log pulling in the Datadog UI: | |
| <br>a. Navigate to [CI Visibility Settings][23] in your Datadog account. | |
| <br>b. Enable log pulling for Azure DevOps. | |
| 2. In Datadog, go to [CI Visibility Settings][23]. | |
| 3. Enable log pulling for Azure DevOps. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do? What is the motivation?
Updates Azure Pipelines CI Visibility documentation to reflect that log collection is now Generally Available (GA):
Merge instructions
Merge readiness:
Additional notes
The translated versions (JA, ES) still contain beta/preview banners - these are managed externally through the translation workflow.