-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Escaping # in metric instance name in telegraf.conf #1546
Comments
what happens if you double-escape it?
|
or also try it with single quotes, with no escaping:
|
Incidentally those are the first two things I tried, but unfortunately neither worked. |
that's unfortunate....might be a bug in the toml parsing library we use then 😕, don't really have time now to track it down but any PRs or additional debugging are greatly appreciated. |
No worries, I'll see what I can do. |
I think i have the same problem, follow config doesn't working
maybe this happens because my nvidia card instance also have # in the name! |
I believe this has been fixed by #1827. |
Bug report
Relevant telegraf.conf:
System info: Windows Server 2012, Telegraf 1.0.0-beta3
Steps to reproduce:
While calling a inputs.win_perf_counters.object, Object type process, I'm running into a problem with having an instance name with a # as part of the instance. On a particular server I have two of the same processes running but I only need to monitor the 2nd. As I label the instance "process#1" for example naturally it comments out the rest of the line. If I attempt to escape it with "process#1" this also breaks the entire process and no results from telegraf are collected.
Expected behavior:
\ should escape the # and allow "process#1" as an instance name for a process
Actual behavior:
"process#1" as an instance name causes Telegraf to relay no data
Additional info:
[[inputs.win_perf_counters.object]]
ObjectName = "Process"
Counters = ["% Privileged Time", "% User Time"]
Instances = ["Ax32Serv#1"]
Measurement = "win_process"
The text was updated successfully, but these errors were encountered: