Dashboard docs suggestions about docs-aspire HOT 3 CLOSED

Overall - talk about the view being live, and that data is only retained for xxx @JamesNK - what is cycling policy for data?

• Executables page - maybe link to docs on how to run an exe as part of Aspire

• Logs pages:

  • Explain that the project/container/exe logs come from the console output of the respective processes. Move the line about OTel up from Project logs to the upper paragraph and use as part of log sources.
  • Structured Logs needs to say it comes from OTLP.

• Traces page should link to https://learn.microsoft.com/en-us/dotnet/core/diagnostics/distributed-tracing.

  • Explain the colors for bars
  • Explain the colors for arrows in the detail view

• Metrics

  • Explain dimensions and how the filtering works
  • Explain that it shows all metrics that have been exported by the app - if its not there its not being exported

from docs-aspire.

Extra addition for Traces page, include an explanation for the different symbols being used

from docs-aspire.

This screenshot shows an extendable "details view" that isn't in preview 1:

Need to get this screenshot again with preview 1's model dialog.

Metrics page

The metrics page docs should discuss filters. The http.server.request.duration is a good example to show. The UI shows attributes with such as http.route with its associated values, routes that metrics have been captured for, in the text box.

By default, all values are included, which means there is no filtering. But you can remove attribute values to filter associated metrics out. For example, removing /image/{imagename} from http.route will filter out all metrics for that route.

from docs-aspire.