# Filebeat unable to collect logs from 'nodeSelector' deployment

**URL:** <https://discuss.elastic.co/t/filebeat-unable-to-collect-logs-from-nodeselector-deployment/343011>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [September 14, 2023, 5:58am UTC](https://discuss.elastic.co/t/filebeat-unable-to-collect-logs-from-nodeselector-deployment/343011 "2023-09-14T05:58:25Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Achu](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/achu/32/125648_2.png) [@Achu](https://discuss.elastic.co/u/Achu)\
**Post date:** [September 14, 2023, 5:58am UTC](https://discuss.elastic.co/t/filebeat-unable-to-collect-logs-from-nodeselector-deployment/343011/1 "2023-09-14T05:58:25Z")

</div>

I’m experiencing a peculiar issue with Filebeat. I can collect logs from all deployments except a couple of deployments that have a node selection. Filebeat Daemonset is running on this node, and I don’t see any errors from Filebeat, but logs are not being collected.

My deployment looks something like this:

```auto
      imagePullSecrets:
        - name: {{ .Values.image.pullSecret | quote }}    
      nodeSelector:
        app: nodeone

```

I also don't have resource issue on this node. Any idea why?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [October 12, 2023, 7:58am UTC](https://discuss.elastic.co/t/filebeat-unable-to-collect-logs-from-nodeselector-deployment/343011/2 "2023-10-12T07:58:58Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.