# How to configure Filebeat to consume logs in JSON format that are already in ECS format **URL:** \ **Category:** Beats\ **Tags:** filebeat\ **Created:** [May 26, 2020, 8:07am UTC](https://discuss.elastic.co/t/how-to-configure-filebeat-to-consume-logs-in-json-format-that-are-already-in-ecs-format/234269 "2020-05-26T08:07:54Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![xprzemekw](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/xprzemekw/32/69056_2.png) [@xprzemekw](https://discuss.elastic.co/u/xprzemekw)\ **Post date:** [May 26, 2020, 8:07am UTC](https://discuss.elastic.co/t/how-to-configure-filebeat-to-consume-logs-in-json-format-that-are-already-in-ecs-format/234269/1 "2020-05-26T08:07:55Z")
Hi, I am new to Elastic and struggling with configuring Filebeat to read logs in JSON that are already in the Elastic Common Schema format. I was inspired by the [https://github.com/elastic/ecs-dotnet/tree/master/src/Elastic.CommonSchema.NLog](https://github.com/elastic/ecs-dotnet/tree/master/src/Elastic.CommonSchema.NLog) project. When properly configured NLog should emit ECS formatted JSON messages to the log file, one message per line. How to configure Filebeat to get them and send to Elastic? I assume logs need no processing as they are already in ECS format, just send to Elastic. How to achieve that? Any guidance welcome 🙂 ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 23, 2020, 8:07am UTC](https://discuss.elastic.co/t/how-to-configure-filebeat-to-consume-logs-in-json-format-that-are-already-in-ecs-format/234269/2 "2020-06-23T08:07:55Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.