# Extracting fields from existing message field in windows logs **URL:** \ **Category:** Logstash\ **Created:** [December 13, 2021, 6:34pm UTC](https://discuss.elastic.co/t/extracting-fields-from-existing-message-field-in-windows-logs/291705 "2021-12-13T18:34:44Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\ **Post date:** [December 13, 2021, 6:59pm UTC](https://discuss.elastic.co/t/extracting-fields-from-existing-message-field-in-windows-logs/291705/2 "2021-12-13T18:59:52Z")
I suspect Most of this would be done for you with the pipelines if you just sent winlogbeat directly to elasticsearch .... if configured correctly... and you run setup etc. I always recommend getting the Beats-\>Elasticsearch architecture working first _before_ introducing Logastash Once you get that working then you can move towards Beats-\>Logstash-\>Elastcsearch Ingest Architecture When you put logstash in the middle some important data is not forwarded unless you use the correctly Here is a post on similar.. its filebeat but the concept is the same > [@Filebeat modules via Logstash](https://discuss.elastic.co/t/filebeat-modules-via-logstash/263612/2): > > Hi @st1988 Welcome the community and thanks for trying the Elastic Stack. It can be a bit challenging the first time you enter into the stack we are working to make this easier with our new feet So here is what I do Macro I make Filebeat to Elasticsearch Work direct first then I route thought Logstash.... if you can not do that thats ok but that is the best way to check if every thing works before routing through logstash 1st) clean up if you have any filbeat indices as the may be not setup… --- _[View the full topic](https://discuss.elastic.co/t/extracting-fields-from-existing-message-field-in-windows-logs/291705)._