# French logs **URL:** \ **Category:** Elasticsearch\ **Created:** [November 24, 2017, 8:34pm UTC](https://discuss.elastic.co/t/french-logs/109081 "2017-11-24T20:34:22Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![s.essa](https://avatars.discourse-cdn.com/v4/letter/s/ecb155/32.png) [@s.essa](https://discuss.elastic.co/u/s.essa)\ **Post date:** [November 24, 2017, 8:34pm UTC](https://discuss.elastic.co/t/french-logs/109081/1 "2017-11-24T20:34:22Z")
Can the Elastic Stack accept and parse logs in French? The logs would be coming from equipment that is configured in french and, for example, fields will be arriving in french. Can ES parse these properly? As far as I can tell, it would simply require the proper configuration of LogStash pipelines. Is this accurate? If you could shed some light on this, I'd be grateful. If you need any information, just ask! 🙂 ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [November 24, 2017, 9:49pm UTC](https://discuss.elastic.co/t/french-logs/109081/2 "2017-11-24T21:49:28Z")
WDYM by « in french »? Can you share an example ? ---
**Author:** ![s.essa](https://avatars.discourse-cdn.com/v4/letter/s/ecb155/32.png) [@s.essa](https://discuss.elastic.co/u/s.essa)\ **Post date:** [November 27, 2017, 2:25pm UTC](https://discuss.elastic.co/t/french-logs/109081/3 "2017-11-27T14:25:58Z")
Hello David, What I mean is that the field names will be in French, for example: instead of "host (origin): IP" the log will say "hôte (origine) : IP" Thanks for the reply. ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [November 27, 2017, 8:28pm UTC](https://discuss.elastic.co/t/french-logs/109081/4 "2017-11-27T20:28:12Z")
I don't see any problem of parsing that. Do you have any issue? ---
**Author:** ![s.essa](https://avatars.discourse-cdn.com/v4/letter/s/ecb155/32.png) [@s.essa](https://discuss.elastic.co/u/s.essa)\ **Post date:** [November 27, 2017, 8:50pm UTC](https://discuss.elastic.co/t/french-logs/109081/5 "2017-11-27T20:50:30Z")
Well, no because I haven't tried it yet. I'm still debating on the use of ELK in our environment and have very little experience with parsing logs. I guess I have 2 questions now, 1. Is there a way to transform these logs into a standardized format, or will that have to be developed? 2. (More generally) Is there such a thing as automatic log acceptance or does the pipeline have to be configured for each log type? ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [November 28, 2017, 12:47pm UTC](https://discuss.elastic.co/t/french-logs/109081/6 "2017-11-28T12:47:57Z")
> Is there a way to transform these logs into a standardized format, or will that have to be developed? If your application can generate OOTB JSON logs, then that will be easier. But this is not the case here I guess. Logstash is indeed one way to parse logs using a grok filter. You can also use an ingest pipeline in elasticsearch using Grok as well. > Is there such a thing as automatic log acceptance or does the pipeline have to be configured for each log type? You need to configure a pipeline per log type. ---
**Author:** ![s.essa](https://avatars.discourse-cdn.com/v4/letter/s/ecb155/32.png) [@s.essa](https://discuss.elastic.co/u/s.essa)\ **Post date:** [November 28, 2017, 2:18pm UTC](https://discuss.elastic.co/t/french-logs/109081/7 "2017-11-28T14:18:51Z")
Thanks a tonne, David. If you don't mind, could you answer a couple more questions? > [@dadoonet](#): > > Logstash is indeed one way to parse logs using a grok filter. You can also use an ingest pipeline in elasticsearch using Grok as well. Are there any other ways? Is there some way to preserve/access the raw log after it has been transformed by Logstash? ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [November 28, 2017, 2:45pm UTC](https://discuss.elastic.co/t/french-logs/109081/8 "2017-11-28T14:45:41Z")
By default logstash keeps the original message intact in message field. ---
**Author:** ![s.essa](https://avatars.discourse-cdn.com/v4/letter/s/ecb155/32.png) [@s.essa](https://discuss.elastic.co/u/s.essa)\ **Post date:** [November 28, 2017, 5:26pm UTC](https://discuss.elastic.co/t/french-logs/109081/9 "2017-11-28T17:26:53Z")
David, you have been incredible, thank you. This all seems like it's very basic and I hate to waste your time. Is there some place I can find information like this? I looked through the documentation but it is too general for me. I need something a little more specific like the questions I'm asking you. ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [November 28, 2017, 9:05pm UTC](https://discuss.elastic.co/t/french-logs/109081/10 "2017-11-28T21:05:05Z")
I think that Logstash Reference guide has a good chapter about this: [https://www.elastic.co/guide/en/logstash/current/first-event.html](https://www.elastic.co/guide/en/logstash/current/first-event.html) ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [December 26, 2017, 9:05pm UTC](https://discuss.elastic.co/t/french-logs/109081/11 "2017-12-26T21:05:06Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.