fix(config): Error on invalid tagpass/tagdrop list syntax#17664
fix(config): Error on invalid tagpass/tagdrop list syntax#17664calvinmachado20 wants to merge 3 commits into
Conversation
|
@calvinmachado20 Thanks for the PR! |
|
@skartikey thanks for having a look at this, I agree with what you said |
|
@skartikey any update on this or is this change good? |
|
It’s worth pointing out that this PR fixes #16398 but does not fix #17500. They may look similar at first, but they are different problems:
|
Co-authored-by: Thomas Casteleyn <thomas.casteleyn@me.com>
|
Download PR build artifacts for linux_amd64.tar.gz, darwin_arm64.tar.gz, and windows_amd64.zip. 📦 Click here to get additional PR build artifactsArtifact URLs |
|
Hello! I am closing this issue due to inactivity. I hope you were able to resolve your problem, if not please try posting this question in our Community Slack or Community Forums or provide additional details in this issue and reqeust that it be re-opened. Thank you! |
|
@skartikey can this PR be opened again? Are there any issues you think with these changes? |
|
Sorry for closing this @calvinmachado20! Are you willing to drive this over the finish line? If so, please rebase the PR on latest master! |
|
Yes, happy to do so. Let me do that and comment back |
Summary
Address open issue: #16398
People work sloppily and try to match metrics with a tagpass = ["mymarkertag"] when the correct version would be tagpass = { "markertag" = ["mymarkertag"] } or similar.
Telegraf doesn't error out, though, and processors and outputs still process and put out the affected metrics because no working tagpass means matching every metric.
But it also matches metrics it shouldn't match and those end up in databases where they shouldn't end up.
Expected behavior
Error out with a config syntax error because tagpass expects a dictionary
Actual behavior
No erroring out and just matching everything leading to metrics in places where they don't belong.
Checklist
Related issues
resolves #16398