Expand dashboard telemetry security guidance

[JamesNK]

Summary

• warn that malicious or compromised senders can submit excessive or maliciously shaped telemetry
• document telemetry spoofing through sender-controlled resource attributes such as service.name
• clarify that storage limits reduce retained memory usage but do not eliminate ingestion-related resource exhaustion
• recommend authentication, network restrictions, gateway limits, telemetry limits, and host monitoring

Validation

• git diff --check
• VS Code MDX diagnostics

[Copilot]

Pull request overview

Expands the Aspire Dashboard security considerations to better communicate ingestion risks from untrusted telemetry senders and to recommend layered mitigations.

Changes:

• Adds explicit warning that OTLP endpoints should only accept telemetry from trusted sources and that sender-controlled resource attributes can enable telemetry spoofing (e.g., service.name).
• Reframes “Memory exhaustion” as broader “Resource exhaustion” and clarifies that storage limits don’t prevent ingestion-time CPU/network/memory pressure.
• Adds defense-in-depth recommendations (auth, network restrictions, gateway limits, telemetry limits tuning, host monitoring).

---

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

[aspire-repo-bot]

Frontend HTML artifact ready

The latest frontend build uploaded the frontend-dist artifact for PR #1396. Use the VS Code button below to open this PR with GitHub Artifacts Explorer and browse the built HTML locally.

This comment updates automatically when a new frontend build artifact is uploaded.