[Discord Feedback] Telemetry & Dashboard documentation gaps #328
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 deployonly 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_docsandaspire-search_docs