David Edler
David Edler
If there is nothing we can do to improve, we should keep the current workaround, yes.
you are free to advance the current implementation to allow you to pass the current state of the board. Out of the box it is not yet possible.
Hello and thanks for the request. Please help me understand the user need a bit better. I understood you want to find out the active instance configuration, including values inherited...
Closing as a duplicate of https://github.com/canonical/lxd-ui/issues/1456
Thanks for raising the request. As far as I know, member cpu and memory utilization is not yet available via the API. I'll check if we can add it there,...
Regarding CPU metrics, those are available but a bit tricky to interpret. Because those are reported as total seconds since instance start. We might add a small graph that is...
> > Regarding CPU metrics, those are available but a bit tricky to interpret. Because those are reported as total seconds since instance start. We might add a small graph...
Added CPU metrics as part of https://github.com/canonical/lxd-ui/pull/1204
Reopening, because host metrics are still not available, only instance cpu metrics. This is related to https://github.com/canonical/lxd-ui/issues/1261
Host metrics are now available as of https://github.com/canonical/lxd-ui/pull/1381 including load average for cpu and memory usage of the cluster members. We do not support temperature as LXD api won't support...