Add Blazor WASM telemetry docs and post-deployment observability guidance

[Copilot]

• Explore existing documentation structure and identify gaps
• Add Blazor WASM section to enable-browser-telemetry.mdx
• Create new dashboard/telemetry-after-deployment.mdx
• Update dashboard.topics.ts sidebar with translations
• CodeQL scan: 0 alerts found
• Doc-tester validation (removed fictional API, fixed package attribution, improved URL guidance)
• Applied @alistairmatthews review suggestions (comment 3968784412):
  • enable-browser-telemetry.mdx: Rephrase trace correlation paragraph (removed parenthetical)
  • enable-browser-telemetry.mdx: Fix proxy code to use HttpRequestMessage instead of mutating client.DefaultRequestHeaders (thread-safety for concurrent requests)
  • telemetry-after-deployment.mdx: "vs." → "versus" in section heading
  • telemetry-after-deployment.mdx: Rephrased UseAzureMonitor() sentence for clarity
  • telemetry-after-deployment.mdx: Rephrased APPLICATIONINSIGHTS_CONNECTION_STRING set-by-Aspire clause
  • telemetry-after-deployment.mdx: "when the OTEL endpoint is configured" → "when you configure the OTEL endpoint"
  • telemetry-after-deployment.mdx: Removed parentheses from list items (if required, when using Azure Monitor)
  • telemetry-after-deployment.mdx: "Container App" → "Container app" in Azure Portal nav path
  • telemetry-after-deployment.mdx: "Telemetry sampled out" → "Telemetry sampling missed an event"
  • telemetry-after-deployment.mdx: Expanded sampling explanation for clarity
  • telemetry-after-deployment.mdx: Removed parentheses around "or similar"
  • telemetry-after-deployment.mdx: Overview → Overview (bolded consistently)
  • telemetry-after-deployment.mdx: "browser token auth" → "browser token authentication"

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[Discord Feedback] Telemetry & Dashboard documentation gaps</issue_title>
<issue_description>## Summary

Based on analysis of 20,415 Discord messages + 147 #help threads (April 2025 - February 2026).

Question counts:

Topic	Questions
Dashboard	140
Configuration	89
OTEL/Telemetry	65
Logs	many (overlaps)

---

Docs That Exist

Slug	Title	Coverage
aspire-dashboard-configuration	Aspire dashboard configuration	✅ Configuration options
use-the-aspire-dashboard-with-nodejs-apps	Dashboard with Node.js	✅ Node.js OTEL
use-the-aspire-dashboard-with-python-apps	Dashboard with Python	✅ Python OTEL

---

Gaps in Existing Docs

1. Frontend/Browser Telemetry (Blazor WASM)

From #help threads:

"How to send OTEL traces from Blazor WASM frontend through authenticated proxy?"

Verified: grep -i "blazor.*otel\|wasm.*telemetry\|browser.*trace" aspire-docs-list.txt returns nothing.

Action Items:

• Blazor WASM OTEL integration
• Browser-to-backend trace correlation
• Authenticated OTEL proxy patterns
• Frontend telemetry collection

---

2. Post-Deployment Logging Issues

From #help threads:

"Only some logs show up in Aspire dashboard after deployed to Azure"

"Inconsistent log collection after Azure deployment"

Action Items:

• Troubleshooting OTEL/logging post-deployment
• Azure Monitor vs Aspire Dashboard integration
• Log collection verification

---

3. Dashboard Access After Deploy

From #help threads:

"After aspire deploy only env-dashboard is accessible, asks for token"

Action Items:

• Dashboard authentication post-deploy
• .env file population after deploy
• Token configuration

---

Data Source

• Discord channels: #💫│general, #🔵│azure, #🔨│building-resources
• Help threads: 147 from #🆘│help
• Total messages: 20,415
• Date range: April 2025 - February 2026
• Verified against: aspire-list_docs and aspire-search_docs</issue_description>

<agent_instructions>Please address this issue, while using the .github/skills/doc-writer/SKILL.md. Be certain to also take into account, related issues, pull requests, and comments that are directly linked as well as comments.</agent_instructions>

Comments on the Issue (you are @copilot in this section)

• Fixes [Discord Feedback] Telemetry & Dashboard documentation gaps #328

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[IEvangelist]

This PR looks good so far, but let's double check it for accuracy by using the .github/skills/doc-tester/SKILL.md skill. Please also consider all new comments and feedback/suggestions. @copilot

[IEvangelist]

Hey @copilot, please have a look at this comment: #455 (review)

[Copilot]

This PR looks good so far, but let's double check it for accuracy by using the .github/skills/doc-tester/SKILL.md skill. Please also consider all new comments and feedback/suggestions. @copilot

Ran doc-tester validation using Playwright against the local dev server. Found and fixed three issues (commit a88f5f8):

1. Removed non-existent API — WithDashboard() had no basis in existing docs or the codebase; replaced with Azure CLI command only
2. Fixed package attribution — Microsoft.Extensions.Azure → Azure.Monitor.OpenTelemetry.AspNetCore as the package that reads APPLICATIONINSIGHTS_CONNECTION_STRING via UseAzureMonitor()
3. Improved "Find dashboard URL" section — replaced a fabricated output format with an Azure CLI command (az containerapp show --query ...) consistent with the existing ACA deployment docs

All internal anchor links (#otlp-configuration, #cors-configuration, #example-browser-telemetry-code, #authenticated-otel-proxy) and all cross-page links verified correct (200 OK). The azurecli language warning in the build is pre-existing in the codebase (e.g. aca-deployment-aspire-cli.mdx).

New page rendering:

Blazor WASM section:

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• telemetry.astro.build
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node node_modules/.bin/../astro/astro.js build (dns block)
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node node_modules/.bin/../astro/astro.js build bash --no�� �� %aE ���� (dns block)
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node node_modules/.bin/../astro/astro.js build e/git log �� %aE ���� --follow git dx -head ules=no ne --no�� �� %aE ���� (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

[Copilot]

Pull request overview

This PR addresses documentation gaps identified from Discord community feedback by adding comprehensive guidance for Blazor WebAssembly telemetry integration and post-deployment observability. The changes fill critical knowledge gaps around browser-based telemetry collection and production telemetry configuration that were frequently asked about in the community.

Changes:

• Added Blazor WASM telemetry integration section to enable-browser-telemetry.mdx covering OTEL config exposure, JS interop initialization, trace correlation, and authenticated proxy patterns
• Created new telemetry-after-deployment.mdx guide explaining development vs. production telemetry differences, Azure Monitor setup, troubleshooting missing logs, and dashboard access after deployment
• Updated sidebar configuration to include the new telemetry after deployment page

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.

File	Description
src/frontend/src/content/docs/dashboard/telemetry-after-deployment.mdx	New comprehensive guide covering production telemetry setup with Azure Monitor, troubleshooting missing logs, and accessing the deployed dashboard
src/frontend/src/content/docs/dashboard/enable-browser-telemetry.mdx	Added Blazor WebAssembly integration section with OTEL configuration API, component initialization, trace correlation, and authenticated proxy pattern
src/frontend/config/sidebar/dashboard.topics.ts	Added sidebar entry for the new telemetry after deployment page

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[alistairmatthews]

@copilot Please implement my suggested changes.

[Copilot]

@copilot Please implement my suggested changes.

Done in commit 2fdf287. All 13 suggestions implemented:

enable-browser-telemetry.mdx

• Removed parentheses from trace correlation paragraph ("such as a Blazor Web App with prerendering" no longer parenthetical)
• Fixed proxy code to use HttpRequestMessage with per-request headers instead of mutating client.DefaultRequestHeaders, preventing thread-safety issues with concurrent requests

telemetry-after-deployment.mdx

• "Development vs. production" → "Development versus production"
• Rephrased package/method sentence: "uses the UseAzureMonitor() method to read this variable and send telemetry"
• Rephrased the Aspire-sets-automatically clause (removed parentheses, "when you reference the resource")
• "when the OTEL endpoint is configured" → "when you configure the OTEL endpoint"
• Removed parentheses from two list items (API key, Application Insights connection string)
• "Container App" → "Container app" in Azure Portal nav path
• "Telemetry sampled out" → "Telemetry sampling missed an event" with expanded explanation
• Removed parentheses around "or similar"
• Overview bolded consistently
• "browser token auth" → "browser token authentication"

[alistairmatthews]

Looks good. Ready to merge.