Skip to content
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

Bug or a feature? #8889

Closed
s-r-engineer opened this issue Feb 20, 2021 · 4 comments
Closed

Bug or a feature? #8889

s-r-engineer opened this issue Feb 20, 2021 · 4 comments
Labels
waiting for response waiting for response from contributor

Comments

@s-r-engineer
Copy link

s-r-engineer commented Feb 20, 2021

SelectorExclude: []string{"*"},

Isn't it a bug to have "*" in that line? Because according to the function Match of IncludeExcludeFilter if you will have anything in "exclude" and anything in "include" then "exclude" will overwrite include. So by default you need to explicit an empty array in config for exclude to avoid that.

@srebhan
Copy link
Member

srebhan commented Feb 22, 2021

Well the mentioned value matches the default documented in the sampleConfig field but does NOT match the text description above the option.

We have two options, either make the options match the text ("all included by default") by changing

SelectorExclude: []string{"*"},```
to
```golang
`SelectorExclude: []string{""},

OR to change the description that everything is _ex_cluded by default.

I think the first option makes more sense, but as this was already be published in releases ppl might rely on this...

@ssoroka, @sspaink, @reimda what do you think?

@sspaink
Copy link
Contributor

sspaink commented Apr 22, 2022

Sorry for the late response, the first option does make more sense but it could break backward compatibility. Maybe for now we update the description, and we could update the option to match the text in 2.0?

We are tracking breaking changes here: #9478

@sspaink sspaink added the waiting for response waiting for response from contributor label Apr 22, 2022
@srebhan
Copy link
Member

srebhan commented Apr 28, 2022

@sspaink I guess the question goes to @PPerminov!? :-)

@telegraf-tiger telegraf-tiger bot removed the waiting for response waiting for response from contributor label Apr 28, 2022
@srebhan srebhan added the waiting for response waiting for response from contributor label Apr 28, 2022
@telegraf-tiger
Copy link
Contributor

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 Page. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
waiting for response waiting for response from contributor
Projects
None yet
Development

No branches or pull requests

3 participants