Skip to content
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

Closed
scaleoutsean opened this issue Feb 9, 2019 · 7 comments
Closed

Graphana UI shows different things with different versions #77

scaleoutsean opened this issue Feb 9, 2019 · 7 comments

Comments

@scaleoutsean
Copy link
Contributor

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.

image

cblomart/vsphere-graphite:50ab88b works fine.

image

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.

@cblomart
Copy link
Owner

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...

@cblomart
Copy link
Owner

As replied to #78 :

Ok, i tried to implement a limit on graphite and there was a bug in it preventing to collect names of entities.
The limit is in place as graphite doesn't have metadata and doesn't need to collect plentity of extra infromations from vsphere.

Can you test with 05a4dc5 ?

@cblomart
Copy link
Owner

Worked for the other issue.
The problem should only have been present with graphite (and not with influx).

@cblomart
Copy link
Owner

Hello @scaleoutsean did you have time to check if the problem is solved by the changes provided?

@scaleoutsean
Copy link
Contributor Author

Maxed out for many consecutive days. Will try this week or weekend and update this comment!

@cblomart
Copy link
Owner

cblomart commented Mar 8, 2019

Ok... as the issue indicated earlier was realy impacting (vm names no longer collected) is solved... i will close the issue.

@cblomart cblomart closed this as completed Mar 8, 2019
@scaleoutsean
Copy link
Contributor Author

Tried v0.8a release, works fine.
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants