# Is Filebeat suitable for local source-code search?

**URL:** <https://discuss.elastic.co/t/is-filebeat-suitable-for-local-source-code-search/323952>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [January 25, 2023, 4:25pm UTC](https://discuss.elastic.co/t/is-filebeat-suitable-for-local-source-code-search/323952 "2023-01-25T16:25:05Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![avistray](https://avatars.discourse-cdn.com/v4/letter/a/85e7bf/32.png) [@avistray](https://discuss.elastic.co/u/avistray)\
**Post date:** [January 25, 2023, 4:25pm UTC](https://discuss.elastic.co/t/is-filebeat-suitable-for-local-source-code-search/323952/1 "2023-01-25T16:25:05Z")

</div>

I have a local folder containing source code and I want to search the files in real time using Elasticsearch. Specifically, I want to use filebeat to monitor files in the folder and send the lines of the files to Elasticsearch.

However, I can't find a pre-made filebeat module that will send the entire line of a text file to Elasticsearch. All of the filebeat modules do some sort of parsing on the line. This makes me think that perhaps I am trying to use the wrong tool for the job.

Is filebeat the best way to search ~10k text files with Elasticsearch or is there a better solution? The advantage of using Elasticsearch over something like ripgrep is that I could enrich the data to include attributes like if the file is code, documentation, or a test.

---

<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:** [February 22, 2023, 6:25pm UTC](https://discuss.elastic.co/t/is-filebeat-suitable-for-local-source-code-search/323952/2 "2023-02-22T18:25:17Z")

</div>

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