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
Configure libvirt input plugin to export cpu stats to influxdb
Expected behavior
Cpu "time" is available as a field in influxdb
Actual behavior
Only "system" and "user" fields are available on InfluxDB.
Additional info
Seems related to InfluxDB "bug" influxdata/influxdb#23024 suggesting "time" cannot be used as a field name. Solution may be to use another name such as using metric prefix like "cpu_time" ?
The text was updated successfully, but these errors were encountered:
@elacour while I agree that naming the field time is unfortunate, renaming it will cause trouble for users of other outputs. So we do have three ways forward:
Keep the current naming and use
[[processors.rename]]
namepass = ["libvirt_cpu"]
[[processors.rename.replace]]
field = "time"dest = "cpu_time"
[[processors.rename.replace]]
field = "user"dest = "cpu_user"
[[processors.rename.replace]]
field = "system"dest = "cpu_system"
Add a flag to prefix the three CPU fields with cpu_ and make this the default in some future.
Rename the fields and add a big fat warning to the readme (and changelog).
I will discuss this with the team and come back to you next week...
I agree that renaming the field can cause trouble. The work around is ok for me, thank you ! I would suggest letting this bug report open to help others with your proposed workaround untile a true rename is included.
Relevant telegraf.conf
Logs from Telegraf
System info
telegraf 1.33.1-1, debian 12, influxdb 2.7.11-1
Docker
No response
Steps to reproduce
Configure libvirt input plugin to export cpu stats to influxdb
Expected behavior
Cpu "time" is available as a field in influxdb
Actual behavior
Only "system" and "user" fields are available on InfluxDB.
Additional info
Seems related to InfluxDB "bug" influxdata/influxdb#23024 suggesting "time" cannot be used as a field name. Solution may be to use another name such as using metric prefix like "cpu_time" ?
The text was updated successfully, but these errors were encountered: