Grafana integration
Croc2828 opened this issue · 8 comments
Hello all !
Sorry to disturb with my issue : I'm able to collect the vcenter information, the influxdb have record on it so I assume it's ok. In Grafana, I just imported the json dashboard, and configured it to use the influx database name. The problem here is that the graph remains empty. I think I'm missing something...
Can you please help ? :)
In the VARIABLES, I've check the query and execute it on the influx itself, and it return nothing :
InfluxDB shell version: 1.5.1
use VMWARE
Using database VMWARE
SHOW TAG VALUES FROM "virtualmachine" with key = "host"
I definitely miss something...
Hello,
could you try
SHOW TAG VALUES FROM "virtualmachine" WITH KEY = "name"
Or
SHOW TAG VALUES FROM "vsphere_virtualmachine" WITH KEY = "name"
@Croc2828 Can you post your config file (or the output from running with -debug), plus the (sanitized) output from:
SHOW DATABASES
SHOW MEASUREMENTS
(the second one might take some time if you have a lot of data on your InfluxDB)
There is probably something going on with database name / prefix.
Adrian
Dear all,
Thanks for the following up 👍
@MicKBfr : The second request is working ! But the SHOW TAG VALUES FROM "vsphere_virtualmachine" WITH KEY = "name" where "host" =~ /^$vCenter$/ return anything.
@sofixa :
SHOW DATABASES
name: databases
name
_internal
VMWARE
use VMWARE
Using database VMWARE
SHOW MEASUREMENTS
name: measurements
name
vsphere_cpu
vsphere_datastore
vsphere_disk
vsphere_hostsystem
vsphere_net
vsphere_resourcepool
vsphere_virtualmachine
Thanks for the support !!!
Here is the settings of the dashboard too, I'm not quiet sure that the query for the vcenter is right.
I've just correct the $vcenter and $vmname variable now. The output are now ok, but I still don't see any data in Grafana.
Hello there,
There is definitely something wrong with the prefix. I've just change the table value and now it's working on GRAFANA. I'm going to remove the prefix from the json config file and let you know.
Ok, I've remove the prefix from the json config file and now it's working !
Thanks for the support.