# Registry not working in filebeat 7.16.1

**URL:** <https://discuss.elastic.co/t/registry-not-working-in-filebeat-7-16-1/292464>\
**Category:** Beats\
**Tags:** docker, filebeat\
**Created:** [December 20, 2021, 1:17pm UTC](https://discuss.elastic.co/t/registry-not-working-in-filebeat-7-16-1/292464 "2021-12-20T13:17:46Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![bbailey](https://avatars.discourse-cdn.com/v4/letter/b/ebca7d/32.png) [@bbailey](https://discuss.elastic.co/u/bbailey)\
**Post date:** [December 20, 2021, 1:17pm UTC](https://discuss.elastic.co/t/registry-not-working-in-filebeat-7-16-1/292464/1 "2021-12-20T13:17:47Z")

</div>

I have recently updated from filebeat 7.7.1 to 7.16.1 running in docker and finding that even though the registry is persisted, each time I restart the filebeat container all logs are being re-read

When I reverted from using the filestream input to the old deprecated log input I find that everything works correctly

is there an additional setting I need to make filestream behave like the log input ?

---

<div class="post-metadata">

**Author:** ![mtojek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mtojek/32/63863_2.png) [@mtojek](https://discuss.elastic.co/u/mtojek)\
**Post date:** [December 20, 2021, 1:39pm UTC](https://discuss.elastic.co/t/registry-not-working-in-filebeat-7-16-1/292464/2 "2021-12-20T13:39:06Z")

</div>

Hi,

could you please describe the environment you're using? Is it a cloud environment? I would be also great to share the filebeat configuration.

---

<div class="post-metadata">

**Author:** ![bbailey](https://avatars.discourse-cdn.com/v4/letter/b/ebca7d/32.png) [@bbailey](https://discuss.elastic.co/u/bbailey)\
**Post date:** [December 20, 2021, 2:05pm UTC](https://discuss.elastic.co/t/registry-not-working-in-filebeat-7-16-1/292464/3 "2021-12-20T14:05:49Z")

</div>

We have a production environment running on physical hardware and a dev environment using aws ec2 instances. I am seeing the issue on both environments

Filebeat is running in docker containers with log file directories mounted within the container

Filebeat input configuration from my test example is below

I 've tested with and without the line "file\_identity.path: ~" which had no effect

```auto
 - type: filestream
      paths:
         - /data/elasticsearch*/logs/*.log
      file_identity.path: ~
      exclude_lines: ["safepoint","gc"]
      parsers:
        - multiline:
            pattern: ^\[
            negate: true
            match: after
      document_type: doc
      ignore_older: 36h
      close_timeout: 36h
      close_removed: true
      clean_removed: true

```

---

<div class="post-metadata">

**Author:** ![bbailey](https://avatars.discourse-cdn.com/v4/letter/b/ebca7d/32.png) [@bbailey](https://discuss.elastic.co/u/bbailey)\
**Post date:** [December 20, 2021, 2:22pm UTC](https://discuss.elastic.co/t/registry-not-working-in-filebeat-7-16-1/292464/4 "2021-12-20T14:22:57Z")

</div>

When I revert to this configuration everything works perfectly

```auto
    - type: log
      paths:
        - /data/elasticsearch*/logs/*.log
      exclude_lines: ["safepoint","gc"]
      multiline:
        pattern: ^\[
        negate: true
        match: after
      document_type: doc
      ignore_older: 36h
      close_timeout: 36h
      close_removed: true
      clean_removed: true

```

---

<div class="post-metadata">

**Author:** ![bbailey](https://avatars.discourse-cdn.com/v4/letter/b/ebca7d/32.png) [@bbailey](https://discuss.elastic.co/u/bbailey)\
**Post date:** [December 31, 2021, 12:16pm UTC](https://discuss.elastic.co/t/registry-not-working-in-filebeat-7-16-1/292464/5 "2021-12-31T12:16:35Z")

</div>

Have you been able to reproduce this issue ?

---

<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:** [January 28, 2022, 2:17pm UTC](https://discuss.elastic.co/t/registry-not-working-in-filebeat-7-16-1/292464/6 "2022-01-28T14:17:09Z")

</div>

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