# Filebeat 7.2.0 autodiscover configuration issues **URL:** \ **Category:** Beats\ **Tags:** filebeat\ **Created:** [June 30, 2019, 3:41am UTC](https://discuss.elastic.co/t/filebeat-7-2-0-autodiscover-configuration-issues/188168 "2019-06-30T03:41:18Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![dnmahendra](https://avatars.discourse-cdn.com/v4/letter/d/5f8ce5/32.png) [@dnmahendra](https://discuss.elastic.co/u/dnmahendra)\ **Post date:** [June 30, 2019, 3:41am UTC](https://discuss.elastic.co/t/filebeat-7-2-0-autodiscover-configuration-issues/188168/1 "2019-06-30T03:41:18Z")
I am trying to setup filebeat for the kubernetes cluster. I am trying to use autodiscover for my containers. I have `istio envoy proxy` running on each pod. I am trying to ship those logs to my elastic stack. But, I am getting following errors - `2019-06-30T07:05:21.816Z ERROR [autodiscover] cfgfile/list.go:96 Error creating runner from config: Fileset envoyproxy/access is configured but doesn't exist` `2019-06-30T07:05:21.816Z ERROR [autodiscover] cfgfile/list.go:96 Error creating runner from config: each input must have at least one path defined` Here is my `yaml` config I using to setup filebeat, ``` apiVersion: v1 kind: ConfigMap metadata: name: filebeat-config namespace: kube-system labels: k8s-app: filebeat data: filebeat.yml: |- setup.dashboards.enabled: true setup.template.enabled: true setup.kibana.host: "192.168.82.162:5601" setup.template.settings: index.number_of_shards: 1 setup.template.overwrite: true filebeat.overwrite_pipelines: true filebeat.autodiscover: providers: - type: kubernetes hints.enabled: true templates: - condition: and: - contains: kubernetes.container.name: swift-client - contains: kubernetes.labels.app: swift-client config: - type: container tail_files: true tags: ["nextjs-server"] pipeline: "nextjs-server" multiline.pattern: 'WARN|ERROR|INFO|DEBUG' multiline.negate: true multiline.match: after containers: ids: - ${data.kubernetes.container.id} - condition: and: - contains: kubernetes.container.name: istio-proxy - contains: kubernetes.labels.app: swift-client - contains: kubernetes.labels.app: swift-server config: - module: envoyproxy access: input: type: container tail_files: true containers: stream: stdout ids: - ${data.kubernets.container.id} error: input: type: container tail_files: true containers: stream: stderr ids: - ${data.kubernetes.container.id} processors: - add_cloud_metadata: ~ - add_host_metadata: ~ - add_kubernetes_metadata: in_cluster: true - add_docker_metadata: output.elasticsearch: hosts: ['${ELASTICSEARCH_HOST:elasticsearch}:${ELASTICSEARCH_PORT:9200}'] ``` I am new to filebeat and any help would be much appreciated! Thanks! ---
**Author:** ![faec](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/faec/32/46988_2.png) [@faec](https://discuss.elastic.co/u/faec)\ **Post date:** [July 3, 2019, 8:44pm UTC](https://discuss.elastic.co/t/filebeat-7-2-0-autodiscover-configuration-issues/188168/2 "2019-07-03T20:44:19Z")
Welcome! I think the first error and possibly the second as well comes from your `envoyproxy` config, where you've put the `input` field underneath the `access` field. I believe `input` should be directly under the module definition, so instead of: ```auto - module: envoyproxy access: input: type: container ... ``` try: ```auto - module: envoyproxy input: type: container ... ``` ---
**Author:** ![dnmahendra](https://avatars.discourse-cdn.com/v4/letter/d/5f8ce5/32.png) [@dnmahendra](https://discuss.elastic.co/u/dnmahendra)\ **Post date:** [July 4, 2019, 12:06am UTC](https://discuss.elastic.co/t/filebeat-7-2-0-autodiscover-configuration-issues/188168/3 "2019-07-04T00:06:01Z")
Hi, Thank you so much that fixes those errors. Now, I have changed my config like this - ```auto apiVersion: v1 kind: ConfigMap metadata: name: filebeat-config namespace: kube-system labels: k8s-app: filebeat data: filebeat.yml: |- setup.dashboards.enabled: true setup.template.enabled: true setup.kibana.host: "192.168.82.162:5601" setup.template.settings: index.number_of_shards: 1 setup.template.overwrite: true filebeat.overwrite_pipelines: true filebeat.config: modules: path: ${path.config}/modules.d/*.yml # Reload module configs as they change: reload.enabled: false filebeat.autodiscover: providers: - type: kubernetes hints.enabled: true templates: - condition.and: - contains: kubernetes.container.name: istio-proxy - contains: kubernetes.labels.app: swift-client - contains: kubernetes.labels.app: swift-server config: input: type: container tail_files: true containers: stream: stdout ids: - ${data.kubernets.container.id} - condition.and: - contains: kubernetes.container.name: swift-client - contains: kubernetes.labels.app: swift-client config: input: type: container tail_files: true tags: ["nextjs-server"] pipeline: "nextjs-server" multiline.pattern: 'WARN|ERROR|INFO|DEBUG' multiline.negate: true multiline.match: after containers: ids: - ${data.container.id} processors: - add_cloud_metadata: ~ - add_kubernetes_metadata: in_cluster: true output.elasticsearch: hosts: ['${ELASTICSEARCH_HOST:elasticsearch}:${ELASTICSEARCH_PORT:9200}'] ``` I am using this - [https://github.com/elastic/beats/tree/master/deploy/kubernetes/filebeat](https://github.com/elastic/beats/tree/master/deploy/kubernetes/filebeat) as reference to write the config. Is there any place I get some detailed docs on how to write this config. or maybe some working examples. Also, are these examples still valid - [https://github.com/elastic/examples/blob/master/MonitoringKubernetes/filebeat-kubernetes.yaml](https://github.com/elastic/examples/blob/master/MonitoringKubernetes/filebeat-kubernetes.yaml) ? I am still seeing the dashboards broken on Kibana, not sure what changes to config I need to make to make the envoyproxy dashboard work on Kibana? ![16%20am](https://us1.discourse-cdn.com/elastic/original/3X/f/8/f86b0bb63b3d6751eb7f1dc858ad733925eb6679.png) ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 1, 2019, 12:16am UTC](https://discuss.elastic.co/t/filebeat-7-2-0-autodiscover-configuration-issues/188168/4 "2019-08-01T00:16:31Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed. ---
**Author:** ![faec](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/faec/32/46988_2.png) [@faec](https://discuss.elastic.co/u/faec)\ **Post date:** [August 29, 2019, 4:39pm UTC](https://discuss.elastic.co/t/filebeat-7-2-0-autodiscover-configuration-issues/188168/5 "2019-08-29T16:39:55Z")
I took another look at this and it seems like a bug in the module; I've [filed an issue](https://github.com/elastic/beats/issues/13420) in the project.