Great video, thank you for the presentation. As the Aspire team realized early on, the dashboard is kind of the shining star of the product. I'm guessing that this is what attracts most devs to Aspire. Let's face it - observability without an intuitive and well-organized UI is not all that useful. I think the interest in the dashboard is a reflection of the frustration we experience trying navigate the logs we have in our Log Analytics, Insights, and Metrics pages in the Azure portal. Trying to find an issue or correlate an event across these views is an exercise in futility. It's a little unfortunate that the dashboard is overshadowing the real strengths of the stack. I am curious about the lack of resource tab in standalone mode. I understand the reason when you're just having it sit there as a listener - it has no context to work with - but could an extra layer be added to allow it to recognize / be configured for an ACA environment? If it knew it was part of an ACA environment, then it could get the resource information it needs. Actually, at that point it could almost be implemented as a feature available directly in the portal as part of the environment. That would be really nice...
Great video, thank you for the presentation. As the Aspire team realized early on, the dashboard is kind of the shining star of the product. I'm guessing that this is what attracts most devs to Aspire. Let's face it - observability without an intuitive and well-organized UI is not all that useful. I think the interest in the dashboard is a reflection of the frustration we experience trying navigate the logs we have in our Log Analytics, Insights, and Metrics pages in the Azure portal. Trying to find an issue or correlate an event across these views is an exercise in futility. It's a little unfortunate that the dashboard is overshadowing the real strengths of the stack.
I am curious about the lack of resource tab in standalone mode. I understand the reason when you're just having it sit there as a listener - it has no context to work with - but could an extra layer be added to allow it to recognize / be configured for an ACA environment? If it knew it was part of an ACA environment, then it could get the resource information it needs. Actually, at that point it could almost be implemented as a feature available directly in the portal as part of the environment. That would be really nice...
the dashboard also automatically works in Production env? or just LOCalhost?