You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
From the portal it is currently very difficult to see the status of all container apps at a glance
Describe the solution you'd like.
From the Container Apps view in the portal have another column with the status of each app. For example whether it is running/stopped/failed/scaled down etc. Even nicer would be the ability to stop and start the apps from the same view
Describe alternatives you've considered.
Clicking into each app but once you have more than 20 odd this can become cumbersome
Additional context.
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
I don’t really mind which view. If one view is easier to construct than the other go for that. However, given the choice of only one we would probably prefer an overall view. It would be quite powerful if you could filter or group by different attributes of the container apps such as environment or resource group.
Having a view in the Container App Environment that includes stats like 'min/max replicas,' 'number of running replicas,' 'memory/CPU assigned,' and similar metrics would be very useful.
Is your feature request related to a problem? Please describe.
From the portal it is currently very difficult to see the status of all container apps at a glance
Describe the solution you'd like.
From the Container Apps view in the portal have another column with the status of each app. For example whether it is running/stopped/failed/scaled down etc. Even nicer would be the ability to stop and start the apps from the same view
Describe alternatives you've considered.
Clicking into each app but once you have more than 20 odd this can become cumbersome
Additional context.
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: