# File beat not generating logs

**URL:** <https://discuss.elastic.co/t/file-beat-not-generating-logs/206729>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [November 6, 2019, 5:50am UTC](https://discuss.elastic.co/t/file-beat-not-generating-logs/206729 "2019-11-06T05:50:34Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Seetharaman\_K](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/seetharaman_k/32/52542_2.png) [@Seetharaman\_K](https://discuss.elastic.co/u/Seetharaman_K)\
**Post date:** [November 6, 2019, 5:50am UTC](https://discuss.elastic.co/t/file-beat-not-generating-logs/206729/1 "2019-11-06T05:50:35Z")

</div>

My file beat is not generating logs . below is the screen shot of the logs folder

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/f/f/ff09b539b191d1559d6f2d012e9620a34c28a0eb.png)  
but i wonder how it is sending logs to ELK server , because i am seeing logs in kibana for today. but there is no evidence that file beats is running. of course its running as a service. but there should be logs for this runs , only then we will come to know what is happening during every run .  
correct ?  
and below is the file beat.yml file

> filebeat.inputs:
> 
> - type: log  
> enabled: true  
> paths:
> - C:/busdata/rrsb/gbl1/logs/\*.log
> 
> filebeat.config.modules:
> 
> # Glob pattern for configuration loading
> 
> path: ${path.config}/modules.d/\*.yml
> 
> # Set to true to enable config reloading
> 
> reload.enabled: true
> 
> output.logstash:  
> hosts: ["10.xxx.100.yyy:5044"]

---

<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:** [December 4, 2019, 5:50am UTC](https://discuss.elastic.co/t/file-beat-not-generating-logs/206729/2 "2019-12-04T05:50:35Z")

</div>

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