From f49a7bb6185381f9abb036a7e2f8523cb22c7464 Mon Sep 17 00:00:00 2001 From: James Newton-King Date: Fri, 9 Oct 2026 09:21:41 +0800 Subject: [PATCH] Update standalone dashboard documentation Removed redundant information about dashboard compilation and startup. --- src/frontend/src/content/docs/dashboard/standalone.mdx | 2 -- 1 file changed, 2 deletions(-) diff --git a/src/frontend/src/content/docs/dashboard/standalone.mdx b/src/frontend/src/content/docs/dashboard/standalone.mdx index d85c446ed..5c91ea115 100644 --- a/src/frontend/src/content/docs/dashboard/standalone.mdx +++ b/src/frontend/src/content/docs/dashboard/standalone.mdx @@ -20,8 +20,6 @@ You can start the dashboard in two ways: Both options receive telemetry from OpenTelemetry-enabled apps. Instrumentation and export configuration are required in each application; starting the dashboard doesn't instrument your code. For language-specific setup, see [Python telemetry](/dashboard/standalone-for-python/) or [JavaScript and Node.js telemetry](/dashboard/standalone-for-nodejs/). -The dashboard is compiled with Native AOT and uses Fluent UI v5. Normal CLI and AppHost startup select the packaged dashboard automatically; you don't need an AOT switch or a separate telemetry configuration. Use the supported dashboard image for container-based deployments. OTLP endpoints, authentication requirements, and persistence settings apply regardless of how you start the dashboard. -