-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Closed
Closed
Copy link
Labels
bugunexpected problem or unintended behaviorunexpected problem or unintended behavior
Description
Relevant telegraf.conf
[[inputs.win_perf_counters]]
[[inputs.win_perf_counters.object]]
ObjectName = "Network Interface"
Counters = ["Bytes Received/sec","Bytes Sent/sec","Packets Received/sec","Packets Sent/sec"]
Instances = ["*"]
Measurement = "root.WinPerfCounters.$COMPUTERNAME.WinNet"
[[outputs.iotdb]]
# host, port, user, password have been purposefully omitted
# to avoid exposing sensitive data
host = ""
port = ""
user = ""
password = ""
uint64_conversion = "int64_clip"
timestamp_precision = "millisecond"
convert_tags_to = "device_id"
timeout = "0s"Logs from Telegraf
2023/12/05 14:59:21 [ERROR] Error Code: 509, Message: [ILLEGAL_PATH(509)] Exception occurred: insertRecord failed. root.WinPerfCounters.DC5.WinNet.Adattatore Ethernet vmxnet3 is not a legal path
2023/12/05 14:59:22 [ERROR] Error Code: 509, Message: [ILLEGAL_PATH(509)] Exception occurred: insertRecord failed. root.WinPerfCounters.DC5.WinNet.isatap.{DAACFE3D-0417-4B20-8F47-9599B4C94381} is not a legal path
System info
Telegraf 1.29.1, Windows Server 2019
Docker
No response
Steps to reproduce
- Configure telegraf to use IoTDB output
- Set convert_tag_to = "device_id"
- Run telegraf in debug mode
Expected behavior
The path should be corrected by enclosing the tags wich contain a character not supported by IoTDB in ``
Actual behavior
Telegraf simply tryes to add the path as it is and dosen't give any way to correct such behaviour
Additional info
Host, port, user, password have been purposefully omitted to avoid exposing sensitive data.
We got a little working fix which is running on our production sites, and are willing to share the current code to get some reviews and maybe improvements.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugunexpected problem or unintended behaviorunexpected problem or unintended behavior