# Where is Filestream integration?

**URL:** <https://discuss.elastic.co/t/where-is-filestream-integration/323245>\
**Category:** Elastic Agent\
**Tags:** filebeat\
**Created:** [January 16, 2023, 11:34am UTC](https://discuss.elastic.co/t/where-is-filestream-integration/323245 "2023-01-16T11:34:41Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Guillaume\_Bouchez](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/guillaume_bouchez/32/115971_2.png) [@Guillaume\_Bouchez](https://discuss.elastic.co/u/Guillaume_Bouchez)\
**Post date:** [January 16, 2023, 11:34am UTC](https://discuss.elastic.co/t/where-is-filestream-integration/323245/1 "2023-01-16T11:34:41Z")

</div>

I'm Using fleet and elastic-agent integration for collecting logs, and I recently discovered a warning from elastic\_agent.filebeat, stating that logs inputs are deprecated and to use filetream inputs instead.

Fine with me, but there is no Filestream Integration package available, only custom log.

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/9/d/9d28d2cec35cf90cde23b9fb2307ea77c8f93df3.png)

Even if Custom Filestream Log is referenced as an integration : [Custom Filestream Logs | Elastic docs](https://docs.elastic.co/integrations/filestream)

And filestream is no where to be found on github package repository : [https://github.com/elastic/integrations/tree/main/packages/filestream](https://github.com/elastic/integrations/tree/main/packages/filestream)

So what is happening here, should we wait for [Replace logfile input using filestream input in all packages · Issue #2495 · elastic/integrations · GitHub](https://github.com/elastic/integrations/issues/2495) to be done and log integration migrated to filestream ? or is there a real custom filestream log integration somewhere ?

---

<div class="post-metadata">

**Author:** ![cmacknz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cmacknz/32/103773_2.png) [@cmacknz](https://discuss.elastic.co/u/cmacknz)\
**Post date:** [January 16, 2023, 3:58pm UTC](https://discuss.elastic.co/t/where-is-filestream-integration/323245/2 "2023-01-16T15:58:25Z")

</div>

We want to migrate all integrations to filestream, however doing that in an automatic way for existing installations requires some enhancements to Filebeat itself to avoid unnecessary data duplication.

Specifically we need to build a way to automatically migrate entries in the Filebeat registry from the log input format to the filestream format. We are actively working on enabling that, [[Design]Automate the migration of `log` input states to `filestream` · Issue #31749 · elastic/beats · GitHub](https://github.com/elastic/beats/issues/31749) is one of the key pieces. A brief overview of the registry itself can be found in [How Filebeat works | Filebeat Reference [8.6] | Elastic](https://www.elastic.co/guide/en/beats/filebeat/current/how-filebeat-works.html#_how_does_filebeat_keep_the_state_of_files)

For now keep using the integration as is and we will provide a way to migrate to filestream easily in the near future.

---

<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 13, 2023, 3:59pm UTC](https://discuss.elastic.co/t/where-is-filestream-integration/323245/3 "2023-02-13T15:59:18Z")

</div>

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