-
Currently deployed aspire dashboard hides so many details about how it's implemented by azure container apps. They should be documented or there should be a way to view the detail deployed aspire dashboard.
All the above is caused by the fact that we can't view Aspire Dashboard resource detail from azure. Is it because the We need to get access to view the Aspire Dashboard resource detail although it may be the internal implementation detail. At least we should be able to view the cost caused by dashboard. |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
The dashboard in ACA is an Azure feature. You don't get to control any details other than what is publicly documented an exposed via the ARM API. You don't get to pick or configure how it is configured and that is by design. As a customer of azure, it's a black box (it could be an azure specific fork for all you know 😉). That said, I think it is fine to document in the ACA documentation the aspire dashboard and what it supports from a public API POV.
There isn't. Can you file an issue here https://github.com/Azure/azure-dev.
You're not paying for it.
That's an implementation detail.
How it works should be documented for sure. |
Beta Was this translation helpful? Give feedback.
-
For future readers: now the Aspire dashboard is charged like any other container (vCPU-s/GiB-s) |
Beta Was this translation helpful? Give feedback.
-
I too am searching for more information since I am actively trying to find a way to get it to work. My ACA environment uses private endpoints which break the aspire dashboard since its not accessible thru its auto-generated url anymore. Been searching for a workaround discussed here: #6960 |
Beta Was this translation helpful? Give feedback.
The dashboard in ACA is an Azure feature. You don't get to control any details other than what is publicly documented an exposed via the ARM API. You don't get to pick or configure how it is configured and that is by design. As a customer of azure, it's a black box (it could be an azure specific fork for all you know 😉).
That said, I think it is fine to document in the ACA documentation the aspire dashboard and what it supports from a public API POV.