[SVLS-8518] Add unlisted Azure App Insights Preview docs#36961
Draft
ryanstrat wants to merge 2 commits into
Draft
[SVLS-8518] Add unlisted Azure App Insights Preview docs#36961ryanstrat wants to merge 2 commits into
ryanstrat wants to merge 2 commits into
Conversation
Add a private (unlisted) guide page introducing the Azure App Insights integration ahead of its Preview launch. The page covers the overview, prerequisites, supported Azure services, request- access flow, and known limitations. It uses private: true so the page is reachable only by direct URL and is excluded from the left nav, search indexing, and noindex behavior.
Contributor
Preview links (active after the
|
Embed a flame-graph screenshot of an Azure App Insights trace rendered in Datadog APM, with the aas.* span attributes visible. The image lives in the conventional path that mirrors the doc's content path, and uses the img shortcode with required alt text.
kimi-p
reviewed
May 28, 2026
|
|
||
| ## How it works | ||
|
|
||
| When your Azure logs are flowing to Datadog and Application Insights is enabled on your workloads, Datadog: |
Contributor
There was a problem hiding this comment.
I think the sequencing of events can be swap for clarity: App Insights is enabled and its logs forwarded.
kimi-p
reviewed
May 28, 2026
Contributor
kimi-p
left a comment
kimi-p
left a comment
There was a problem hiding this comment.
Couple of comments. Otherwise, LGTM!
| - Azure Storage | ||
| - Azure Cosmos DB | ||
| - Azure API Management | ||
| - Azure SQL Database |
| 1. Reads App Insights records from your forwarded Azure logs. | ||
| 2. Converts each App Insights operation into a Datadog APM span, preserving parent-child relationships across both the legacy hierarchical Request-Id format and W3C Trace Context. | ||
| 3. Enriches spans for [supported Azure services](#supported-azure-services) with Azure resource metadata, including resource group, subscription, region, and resource tags. | ||
| 4. Ingests the spans through the standard APM pipeline. |
|
|
||
| ## Prerequisites | ||
|
|
||
| Before you can use the Azure App Insights Integration, set up the following: |
Contributor
There was a problem hiding this comment.
I think we'll need to clearly specify that this solution only supports v2 but not v3 and point them to v3 OTel doc?
| Before you can use the Azure App Insights Integration, set up the following: | ||
|
|
||
| 1. **Enable Azure Application Insights** on the Azure workloads you want to trace. | ||
| 2. **Install the [Microsoft Azure integration][1].** It provides both the log forwarding path and the Azure resource metadata used for enrichment. |
Contributor
There was a problem hiding this comment.
Should we specifically call out for Azure Automated Log Forwarding Setup and enabling metrics/resource collection? There seems to have too many content and I'd assume most customers already have basic azure integrations.
|
|
||
| The Azure App Insights Integration is in Preview. To request access, sign up through the [Preview form](https://www.datadoghq.com/product-preview/). | ||
|
|
||
| After you submit the form, the Datadog team responds within one week with installation instructions and next steps. |
Contributor
There was a problem hiding this comment.
I don't think there's more instructions and next steps beyond what's on the doc?
|
|
||
| - **Preview status.** The integration is in public Preview with a limited design-partner cohort. Access is granted after sign-up through the Preview form. | ||
| - **Resource metadata enrichment is service-specific.** Spans for Azure services outside the [supported list](#supported-azure-services) are converted but not enriched with Azure resource metadata. | ||
| - **Mixed-format trace hierarchy depends on span links.** Some Azure workloads emit a mix of the legacy hierarchical Request-Id format and W3C Trace Context. Datadog represents this transition as a [span link][3], allowing navigation between related traces. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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?
Fixes SVLS-8518.
Adds a new unlisted (
private: true) guide page introducing the Azure App Insights integration ahead of its Preview launch. The page is reachable only by direct URL — not surfaced in the left navigation or site search — so the URL can be shared from the Preview signup form.The page covers:
New page:
content/en/tracing/guide/serverless_enable_azure_app_insights.mdMerge instructions
Merge readiness:
Additional notes
One open TODO is intentionally left in the file as an HTML comment: the Preview form URL placeholder should be replaced with the integration-specific form URL before the page is shared publicly.