Skip to content

Document dashboard data persistence - #1649

Merged
David Pine (IEvangelist) merged 2 commits into
release/13.6from
docs/dashboard-data-persistence
Sep 11, 2026
Merged

David Pine (IEvangelist) merged 2 commits into
release/13.6from
docs/dashboard-data-persistence

Conversation

@JamesNK

Copy link
Copy Markdown
Member

Summary

  • Add a detailed dashboard data persistence page covering persistence modes, run history, storage, retention, and compatibility.
  • Document persistence configuration for AppHost, CLI, and standalone container scenarios.
  • Update dashboard overview, deployment guidance, and security considerations for persisted telemetry.

Documents the dashboard persistence behavior introduced by microsoft/aspire#18924.

Third-party links and affiliations

None.

Validation

  • git diff --check
  • src/frontend/node_modules/.bin/eslint.cmd src/frontend/config/sidebar/dashboard.topics.ts
  • VS Code diagnostics for the modified MDX files

The full frontend test suite was not run because the local dependency installation is incomplete and completing it would require downloading packages.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changes recommended

Correct the AppHost configuration paths and clarify persistence defaults before approval.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

Documents dashboard data persistence, including modes, storage, retention, configuration, and security.

Changes:

  • Adds a dedicated persistence guide.
  • Documents AppHost, CLI, and standalone container configuration.
  • Updates deployment, overview, security, and navigation documentation.
File summaries
File Reviewed change
src/frontend/src/content/docs/dashboard/telemetry-after-deployment.mdx Updates deployment telemetry guidance.
src/frontend/src/content/docs/dashboard/standalone.mdx Adds standalone persistence instructions.
src/frontend/src/content/docs/dashboard/security-considerations.mdx Documents persisted-data security considerations.
src/frontend/src/content/docs/dashboard/overview.mdx Highlights dashboard persistence capabilities.
src/frontend/src/content/docs/dashboard/data-persistence.mdx Adds persistence modes, storage, retention, and compatibility guidance.
src/frontend/src/content/docs/dashboard/configuration.mdx Adds persistence configuration references and examples.
src/frontend/src/content/docs/app-host/configuration.mdx Adds AppHost persistence settings.
src/frontend/config/sidebar/dashboard.topics.ts Adds the persistence page to navigation.
Review details

Suppressed comments (2)

src/frontend/src/content/docs/dashboard/configuration.mdx:125

  • This replacement repeats the same C# AppHost issue in the common configuration table: aspire.config.json is not the launch-profile file for project-based or file-based C# AppHosts. Please refer to the selected AppHost launch profile (with the language-specific locations documented at /app-host/configuration/) instead of naming only aspire.config.json.
| `ASPIRE_DASHBOARD_OTLP_HTTP_ENDPOINT_URL`<br/>Default: `http://localhost:18890` | The [OTLP/HTTP](https://opentelemetry.io/docs/specs/otlp/#otlphttp) endpoint. This endpoint hosts an OTLP service and receives telemetry using Protobuf over HTTP. When the dashboard is launched by the Aspire AppHost the OTLP/HTTP endpoint isn't configured by default. To configure an OTLP/HTTP endpoint with the AppHost, set an `ASPIRE_DASHBOARD_OTLP_HTTP_ENDPOINT_URL` environment variable in an _aspire.config.json_ launch profile. Securing the dashboard with HTTPS is recommended. |

src/frontend/src/content/docs/dashboard/telemetry-after-deployment.mdx:20

  • The table's Temporary by default wording is misleading for the main Aspire scenario: the AppHost-launched dashboard defaults to Run persistence, while only standalone mode defaults to None. A reader following this page would incorrectly expect AppHost telemetry to disappear on every restart; distinguish the AppHost and standalone defaults here.
| **Retention** | Temporary by default; persistence is configurable | Configurable (days, months, indefinitely) |
  • Files reviewed: 8/8 changed files
  • Comments generated: 2
  • Review effort level: Lite

💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment on lines +28 to +30
The AppHost automatically configures the dashboard, but you can override values if needed. The recommended way to configure the dashboard from the AppHost is to add environment variables to a launch profile in _aspire.config.json_. This configuration works with both C# and TypeScript AppHosts.

```json title="launchSettings.json" {14}
```json title="aspire.config.json" {6}
- Real-time tracking of logs, traces, and environment configurations.
- User interface to [stop, start, and restart resources](/dashboard/explore/#resource-actions).
- Collects and displays logs and telemetry; [view structured logs, traces, and metrics](/dashboard/explore/#monitoring-pages) in an intuitive UI.
- Persists resources and telemetry so you can inspect and compare completed application runs.
@aspire-repo-bot

Copy link
Copy Markdown
Contributor

Frontend HTML artifact ready

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

VS Code: Open PR #1649 artifacts

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

Updated data persistence documentation to include FileTree component for data layout visualization.
@IEvangelist
David Pine (IEvangelist) merged commit 1b26490 into release/13.6 Sep 11, 2026
10 checks passed
@IEvangelist
David Pine (IEvangelist) deleted the docs/dashboard-data-persistence branch September 11, 2026 12:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants