# Beat fields and logstash filters **URL:** \ **Category:** Logstash\ **Created:** [April 17, 2019, 4:30pm UTC](https://discuss.elastic.co/t/beat-fields-and-logstash-filters/177341 "2019-04-17T16:30:26Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![4rakasi](https://avatars.discourse-cdn.com/v4/letter/4/7cd45c/32.png) [@4rakasi](https://discuss.elastic.co/u/4rakasi)\ **Post date:** [April 17, 2019, 4:30pm UTC](https://discuss.elastic.co/t/beat-fields-and-logstash-filters/177341/1 "2019-04-17T16:30:26Z")
Hello, With the upgrade to version 7.0.0, many fields have been changed for beats agent. My template have been updated regarding those changes, however I have a problem with my logstash filters. I created those filters based on the following [documentation](https://www.elastic.co/guide/en/logstash/7.0/logstash-config-for-filebeat-modules.html). However, in the current documentation, fields have not been updated yet and still uses old fields. This highlighted the fact that logstash filters can become difficult to maintain for me. My first question is: Q1: Is there a way to create logstash filters based on beats fields.yml so that logs can be easily parsed? There is currently the following [script](https://www.elastic.co/guide/en/logstash/current/ingest-converter.html) that convert ingest nodes configuration to logstash configuration, but it doesn't seem to work with fields.yml files. My second question is regarding template management with logstash. Q2: Is there a way to manage beats template (that is to say with the fields.yml file) directly from logstash using the manage\_template option as it seems it only recognize template in json format ? Thanks ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [May 15, 2019, 4:30pm UTC](https://discuss.elastic.co/t/beat-fields-and-logstash-filters/177341/2 "2019-05-15T16:30:33Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.