Which specific part? The dashboard works anywhere in an app that you can add opentelemetry to. The aspire orchestration and integration should work just fine in a .net 8 Blazor app
Aspire dashboard is great for simplicity, but sadly not production-ready. It doesn't persist dashboard data, and for 'Metrics' u can only look data up to 12 hours ago. We need data starting from day 1 until the present moment. It would be great, if it can use volume to persist data.
It’s for local dev productivity and real-time first and foremost. For production is a nice option to have but also there are lots of great services out there like azure monitor
The challenge I think many people have is finding a fully integrated tracing/logging/metrics open-source dashboard like this in production. Most "how-tos" recommend one OSS tool for traces, one for logs, another for metrics. On the commercial side there are integrated views in Azure Monitor, NewRelic, etc but they come at a high cost (ingestion, monthly fee, complexity). If someone could extend the Aspire Dashboard with 30 day memory from cheap storage it would easily become the default for small to medium deployments.
i really dislike the notion of certain tools being 'development env only'. sure, it helps during development, but i want my dev env to be as close to production as possible so that i can spot any nuances early, and/or be able to replicate issues that arise. not to mention that i want to be able to practice using the tools available to me on production so that i can understand them better.
For production you can flip on the Aspire Dashboard in azure container apps or deploy yourself. However, really a tool like Azure Monitor would give you the best production results
@@JamesMontemagno been there, azure monitor turned out to be too expensive. now my project is using prometheus, jaeger, seq and grafana for application observability
I watched several videos on the subject and this is the first one that allowed me to 'get it'
Nice video! Is there a way we can add projects from other solutions?
I have a python api. Is there a way to add metrics for that?
Yup! Just add open telemetry. Checkout the sample in the description
Will this work with Blazor Standalone? Or is it only the new templates?
Which specific part?
The dashboard works anywhere in an app that you can add opentelemetry to.
The aspire orchestration and integration should work just fine in a .net 8 Blazor app
@JamesMontemagno Great, I hope it can work because we've been trying to add Aspire to our Blazor wasm app (Not the server client wasm)
super cool James. how we can use this aspire dashboard over kubernetes (AKS) and go beyond local to production?
Can deploy it as a container and configure your services to pipe in telemetry
@@JamesMontemagno can i use persistance vol to store opentelemetry data ?
Not sure would ask on the aspire GitHub
Aspire dashboard is great for simplicity, but sadly not production-ready.
It doesn't persist dashboard data, and for 'Metrics' u can only look data up to 12 hours ago.
We need data starting from day 1 until the present moment. It would be great, if it can use volume to persist data.
It’s for local dev productivity and real-time first and foremost. For production is a nice option to have but also there are lots of great services out there like azure monitor
The challenge I think many people have is finding a fully integrated tracing/logging/metrics open-source dashboard like this in production. Most "how-tos" recommend one OSS tool for traces, one for logs, another for metrics. On the commercial side there are integrated views in Azure Monitor, NewRelic, etc but they come at a high cost (ingestion, monthly fee, complexity). If someone could extend the Aspire Dashboard with 30 day memory from cheap storage it would easily become the default for small to medium deployments.
Please use it with next js
ua-cam.com/video/YKraN1ZETpw/v-deo.htmlsi=lIelPWx4VQckMg6T
i really dislike the notion of certain tools being 'development env only'. sure, it helps during development, but i want my dev env to be as close to production as possible so that i can spot any nuances early, and/or be able to replicate issues that arise. not to mention that i want to be able to practice using the tools available to me on production so that i can understand them better.
For production you can flip on the Aspire Dashboard in azure container apps or deploy yourself. However, really a tool like Azure Monitor would give you the best production results
@@JamesMontemagno been there, azure monitor turned out to be too expensive. now my project is using prometheus, jaeger, seq and grafana for application observability
It's free?
Yup! Free and open source