You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
...Drop measurement vsphere_host_cpu from influxdb
...Restart telegraf and Influxdb
Expected behavior:
Incoming CPU core count data to be in the correct order
Actual behavior:
Incoming CPU core count data is out of order
Additional info:
I am using Influxdb along with Telegraf and the vSphere Input Plugin to visualize data in Grafana and one of my graph keeps track of my CPU utilization. Recently I upgraded my host’s CPU to one with a bigger core count but now the legend is out of order:
I have tried dropping the measurement responsible from the database (vsphere_host_cpu) and restarting both Influx and Telegraf but it still comes back unordered.
I opened an issue at Grafana but was told this was a database issue so I opened an issue with Influxdb but was told data is coming in unordered and there's nothing I can do. Perhaps someone here can help?
The text was updated successfully, but these errors were encountered:
System info:
Telegraf v1.14.3
Ubuntu 18.04
Docker
Steps to reproduce:
Expected behavior:
Incoming CPU core count data to be in the correct order
Actual behavior:
Incoming CPU core count data is out of order
Additional info:
I am using Influxdb along with Telegraf and the vSphere Input Plugin to visualize data in Grafana and one of my graph keeps track of my CPU utilization. Recently I upgraded my host’s CPU to one with a bigger core count but now the legend is out of order:
I have tried dropping the measurement responsible from the database (vsphere_host_cpu) and restarting both Influx and Telegraf but it still comes back unordered.
I opened an issue at Grafana but was told this was a database issue so I opened an issue with Influxdb but was told data is coming in unordered and there's nothing I can do. Perhaps someone here can help?
The text was updated successfully, but these errors were encountered: