The Aspire dashboard is a shared view of the resources and telemetry in an orchestrated application. Launch the AppHost to start the application’s resources together, then open the dashboard to see which services are running and inspect their behavior from one place. section 1.0 section 1.6
Use the tabs for different operational questions:
- Resources: Check each service’s type, name, state, source project, and available endpoints. The state indicates whether a service is running and healthy. section 1.6
- Console: Read the console logs for an individual service. Structured: Inspect structured logs across services. section 1.6 section 6.4
- Traces and Metrics: Examine recorded activity and measurements across the application. section 6.4
Follow a storefront-to-API flow
Run OnlineShop.AppHost and wait for the services to build. In Resources, confirm that OnlineShop.Web and the API are running, then open the web application’s endpoint. Its Blazor UI retrieves data from the API; return to the dashboard to inspect the services’ logs, traces, or metrics. An HTTP launch profile may show one endpoint per service instead of two in this local-development setup. section 1.6 section 6.4
The dashboard brings together observations about what happened; checking whether an application is working correctly right now also calls for a separate mechanism. Secure dashboard access as well: its default security option is a URL token, and other security configuration options are available. section 6.4 section 8.6
