How to persist and display data with Aspire standalone dashboard #2564
-
|
Hello Aspire Team, I have tried the new standalone dashboard and I think it's great! Great work and I'm excited to see what else is coming. As I am not yet an expert in the .NET Core Framework myself, I have a question. In general, the issue is that currently displayed data is gone after restarting the dashboard container. How can I make it so that such data can be saved and then displayed again so that I can also see historical data? What is the recommended way when using the standalone dashboard? If this could somehow work without using the whole stack from e.g. Prometheus, Grafana, Tempo, Loki, that would be great. I favour a lightweight solution. Best regards and great work |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 3 replies
-
|
There's no support for persisting the telemetry data and no plans to implement external storage. When you restart the dashboard, the data is lost. Treat this dashboard like your volatile telemetry source, not a long-term data store for telemetry. For historical data, you need a real production ready telemetry system. The dashboard outside of developer scenarios works best as one of the targets for telemetry data instead of being the only one (especially if you want historical data). |
Beta Was this translation helpful? Give feedback.
-
|
Many thanks for the quick reply :-) |
Beta Was this translation helpful? Give feedback.
-
|
We hope that future versions will consider adding a feature for storing telemetry data. This is particularly important for smaller-scale application projects, which, in the early stages of development, often do not have a large number of services and telemetry data. However, to achieve the storage and display of telemetry data, it is necessary to deploy a significant amount of middleware services, which can be a challenge for projects with limited resources. Therefore, a simplified telemetry monitoring service that supports data persistence would be greatly beneficial, especially for developers in the early stages of their projects. |
Beta Was this translation helpful? Give feedback.
-
|
I can't predict what will happen in the future, but we have no plans, even for small shops, to persist the data outside of the dashboard. Building a durable telemetry storage system is a project by itself, the UI is easy in comparison. |
Beta Was this translation helpful? Give feedback.
-
|
@expcat @SirPustekuchen - came across this article, hope this helps https://blog.datalust.co/persistent-logs-and-traces-for-the-net-aspire-dashboard/
|
Beta Was this translation helpful? Give feedback.
There's no support for persisting the telemetry data and no plans to implement external storage. When you restart the dashboard, the data is lost. Treat this dashboard like your volatile telemetry source, not a long-term data store for telemetry.
For historical data, you need a real production ready telemetry system. The dashboard outside of developer scenarios works best as one of the targets for telemetry data instead of being the only one (especially if you want historical data).