-
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
Docker input: add include/exclude filters for container names. #2734
Comments
The standard way we would do this is to have an include list and an exclude list, both would have glob patterns. The same as for tagpass/tagdrop. I'm open to regex but we need to decide on a nice way to expose them in a backwards compatible way, there was a little discussion about this yesterday on #2726.
Seems like a nice feature, can you open a separate feature request for this? I'm going to rename this issue for the first request. |
@danielnelson, sounds good. One could add two more configuration parameters which should deprecate the container_names option in the future.
I'd suggest aliasing container_names to include_container_names. If users are using container_names, each element can be turned into a regex like '^name$'. This will keep backwards compatibility. |
Lets name them |
I will get started on this. Would you want to retain the current container_name option for backward compatibility? |
Yeah, leave the current option in but document it as deprecated. Thanks |
adding wildcard support for container inclusion/exclusion. Solves influxdata#2734.
adding wildcard support for container inclusion/exclusion. Solves influxdata#2734.
Merged for 1.4.0 |
It would be handy if the docker input plugin supported (regex) patterns in container names.
It'd be even nicer to have an include/exclude boolean option to drive the logic behind container_names.
Also, I noticed the plugin keeps reporting metrics for containers in exit state. Not sure what the reason is behind this, but maybe one can provide an option to disable this behavior?
The text was updated successfully, but these errors were encountered: