You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add shared tracing setup (agent-tracing-setup.md) and fresh stored-trace verification (agent-tracing-verification.md) references, and link them from the native, hosted quickstart/redeploy, project-create and ordinary-prompt workflows.
Add a pre-provisioning preflight: check native monitoring capability and opt-out, handle a network: block (private networking is unsupported, so set monitoring.enabled: false), and get billing/privacy approval before creating App Insights. Existing projects only connect a user-supplied component ID.
Align with azd: new projects get App Insights and an AppInsights connection by default, and a monitoring failure fails azd provision (reported as a provision failure). Optional access and verification failures still warn and continue.
Document that each user needs Log Analytics Reader on the App Insights resource to read traces; azd does not grant it.
Preserve working shared/Entra connections, prefer nonsecret resource IDs, and note that ejected Terraform now includes monitoring.
Unrelated CI fix: raise the telemetry installer digest test timeout to 30s (it exceeds Vitest's 5s default on main too).
Validation
npm run references and validate-stimulus pass.
All four offline tracing evals (tracing.eval.yaml) pass every trial: 5 trials per case, 20/20, using claude-sonnet-5 as both agent and judge (the default judge model is unavailable). Run against a fresh npm run build output, since evals read output/, not plugins/.
Native e2e (new, off, existing-BYO, Bicep, Terraform) was run before the final azd rebase. Traces were seen in the Foundry portal, but post-rebase trace verification is not re-confirmed.
The token check still fails on pre-existing oversized files; these edits add small increments.
Give the digest-mismatch installer test the adjacent download test's
30-second budget. Both main and this PR exceed Vitest's five-second
default while running the PowerShell installer case.
Preserve every digest-rejection assertion. Runtime behavior and global
CI timeout settings are unchanged.
Authored-by: GitHub Copilot CLI 1.0.100
Model: GPT-6.1 Sol (gpt-6.1-sol)
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: ebefc78f-0541-4087-837a-f5eeb5a358a5
The reason will be displayed to describe this comment to others. Learn more.
🟡 Changes recommended
Monitoring provisioning occurs before required charges/privacy approval and capability/opt-out checks, and tracing overlooks the starter’s exported resource ID.
Adds shared tracing setup and verification guidance to Foundry agent workflows, separating deployment and invocation success from evidence of fresh stored traces.
Changes:
Connects project creation, hosted deployment, prompt deployment, and smoke invocation workflows to shared tracing guidance.
Preserves existing connections and approval boundaries while preferring nonsecret destination identifiers.
Adds three offline tracing evaluations and increases one telemetry-download test timeout.
File
Description
scripts/src/__tests__/telemetry-hooks.test.ts
Raises checksum-failure test timeout to 30 seconds.
The reason will be displayed to describe this comment to others. Learn more.
🟡 Changes recommended
Provisioning can create monitoring resources or write project connections before the required monitoring cost/privacy and connection-write approvals are obtained.
This preflight covers only new projects, but Step 2 also provisions infrastructure against existing projects. With monitoring.applicationInsightsResourceId configured, the companion native implementation can write the project connection during provisioning, before Step 3 requests approval. Apply the preflight to existing-project provisioning too, requiring connection-write approval naming the project and component before azd provision.
…e/deploy flows
Address review: remove tracing paragraph from SKILL.md, keep only a Yes/No monitoring row in quickstart/create-hosted, drop preflight and polling from deploy/invoke/create-project, move agent-tracing references under foundry-agent/trace/references, and align network: handling and evals with merged azd behavior.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: c1d0003f-40c8-481d-92a5-ecb8d7afb491
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
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.
Summary
agent-tracing-setup.md) and fresh stored-trace verification (agent-tracing-verification.md) references, and link them from the native, hosted quickstart/redeploy, project-create and ordinary-prompt workflows.network:block (private networking is unsupported, so setmonitoring.enabled: false), and get billing/privacy approval before creating App Insights. Existing projects only connect a user-supplied component ID.AppInsightsconnection by default, and a monitoring failure failsazd provision(reported as a provision failure). Optional access and verification failures still warn and continue.tracing.eval.yaml): custom IaC failure, query denial, hosted correlation, native provision failure.maintoo).Validation
npm run referencesandvalidate-stimuluspass.tracing.eval.yaml) pass every trial: 5 trials per case, 20/20, usingclaude-sonnet-5as both agent and judge (the default judge model is unavailable). Run against a freshnpm run buildoutput, since evals readoutput/, notplugins/.Companion azd PR: Azure/azure-dev#10743