Open kpfaulkner opened 5 years ago
Actually, this might be my error... I did the grafana-cli command to upgrade... it succeeded but I noticed in the UI that it still says 0.2.0 after a restart. Investigating.
Ok, have now really upgraded to 0.3.0 (I think the initial upgrade was via another account)... but now the ONLY namespace showing up is "microsoft.insights/autoscalesettings"... and nothing else.
No errors at least... but not useful (particularly since I'm after CPU/Memory usage).
I updated the whitelist for Azure Monitor metrics to not show namespaces where there are no metrics available. ClassicCompute is one of those namespaces. I will however be adding support for some classic namespaces in the near future - it requires a change to the code as the api calls for them are different from the rest of the metrics.
Hi
I've tried version 0.3.0 against Azure and it doesn't appear to be different to version 0.2.0. Screenshot attached of what I'm seeing.
Basically resource group can be selected, but only a single namespace is available in the dropdown option. When I try and hit save I get a huge list of namespaces that are available (although only 1 was through the combo box).
Got the same issue with 0.2.0
Ken