# Filebeat modules ECS 8.0 support plan

**URL:** <https://discuss.elastic.co/t/filebeat-modules-ecs-8-0-support-plan/321797>\
**Category:** Beats\
**Tags:** ecs-elastic-common-schema, filebeat\
**Created:** [December 21, 2022, 9:19pm UTC](https://discuss.elastic.co/t/filebeat-modules-ecs-8-0-support-plan/321797 "2022-12-21T21:19:36Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![brsolomon](https://avatars.discourse-cdn.com/v4/letter/b/8491ac/32.png) [@brsolomon](https://discuss.elastic.co/u/brsolomon)\
**Post date:** [December 21, 2022, 9:19pm UTC](https://discuss.elastic.co/t/filebeat-modules-ecs-8-0-support-plan/321797/1 "2022-12-21T21:19:36Z")

</div>

It appears that all Filebeat modules currently export ECS version 1.12 fields.

Running command from `beats/x-pack/filebeat/module`:

```auto
$ ggrep -Fr 'ecs.version: 1.12' | wc -l
     140

brsolomon ~/dev/3pty/beats/x-pack/filebeat/module -> main
$ ggrep -Fr 'ecs.version: 8' | wc -l
       0

```

- Is there a plan and/or timeline to update modules to export [ECS 8.0 schemas](https://www.elastic.co/guide/en/ecs/current/ecs-release-notes-8.0.0.html)?
- Would this mean dropping support for exporting the 1.12 versions, or would the goal be for dual compatibility?

---

<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 18, 2023, 11:20pm UTC](https://discuss.elastic.co/t/filebeat-modules-ecs-8-0-support-plan/321797/2 "2023-01-18T23:20:17Z")

</div>

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