Skip to content
Docs Try Aspire
Docs Try

Aspire dashboard overview

Aspire project templates include a sophisticated dashboard for comprehensive app monitoring and inspection. The dashboard is also available in standalone mode.

The dashboard enables real-time tracking of key aspects of your app, including logs, traces, and environment configurations. It’s designed to enhance the development experience by providing a clear and insightful view of your app’s state and structure.

Key features of the dashboard include:

The dashboard is integrated into the Aspire *.AppHost. During development the dashboard is automatically launched when you start the project. It’s configured to display the Aspire project’s resources and telemetry.

A screenshot of the Aspire dashboard Resources page.

For more information about using the dashboard during Aspire development, see Explore dashboard features.

The Aspire dashboard can run standalone, without the rest of Aspire. The standalone dashboard provides a great UI for viewing telemetry and can be used by any application that sends OpenTelemetry data. You can start it with the Aspire CLI or run it from the standalone container image. For more information, see the Standalone Aspire dashboard.

The dashboard is configured when it starts up. Configuration includes frontend and OTLP addresses, the resource service endpoint, authentication, telemetry limits and more.

For more information, see Aspire dashboard configuration.

The dashboard user experience is built with a variety of technologies. The frontend communicates with the resource server over gRPC using the Grpc.AspNetCore NuGet package. Consider the following diagram that illustrates the architecture of the Aspire dashboard:

A diagram showing the architecture of the Aspire dashboard.

The Aspire dashboard offers powerful insights to your apps. The UI displays information about resources, including their configuration, console logs and in-depth telemetry.

Data displayed in the dashboard can be sensitive. For example, configuration can include secrets in environment variables, and telemetry can include sensitive runtime data. Care should be taken to secure access to the dashboard.

For more information, see Aspire dashboard security considerations.