-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Graphana UI shows different things with different versions #77
Comments
On your first screenshot it seems it takes performance metric names in place of vm names. I presume you are using influxdb as a backend? I will try to dublicate that in a lab... |
Worked for the other issue. |
Hello @scaleoutsean did you have time to check if the problem is solved by the changes provided? |
Maxed out for many consecutive days. Will try this week or weekend and update this comment! |
Ok... as the issue indicated earlier was realy impacting (vm names no longer collected) is solved... i will close the issue. |
I changed several things at once (not a good idea). so it took me several hours to narrow this down a bit - it seems that a recent vsphere-graphite container works differently compared to 1-2 months ago.
cblomart/vsphere-graphite:eaa6a13
results in no VMs but different things appearing in VM drop-down list.cblomart/vsphere-graphite:50ab88b
works fine.I used the two versions above with
graphiteapp/graphite-statsd:1.1.5-7
for graphite-statsd (which is the second major change in this case, as previously I used graphite-statsd v0.8.0). My vSphere/ESXi are v6.7.cblomart/vsphere-graphite:50ab88b worked fine with the old graphite-statsd v0.8.0, but I haven't tested cblomart/vsphere-graphite:eaa6a13 with that old graphite-statsd version.
The text was updated successfully, but these errors were encountered: