# Groks for parsing Windows and Redhat syslogs

**URL:** <https://discuss.elastic.co/t/groks-for-parsing-windows-and-redhat-syslogs/93071>\
**Category:** Logstash\
**Created:** [July 13, 2017, 7:08pm UTC](https://discuss.elastic.co/t/groks-for-parsing-windows-and-redhat-syslogs/93071 "2017-07-13T19:08:07Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![CDR](https://avatars.discourse-cdn.com/v4/letter/c/d9b06d/32.png) [@CDR](https://discuss.elastic.co/u/CDR)\
**Post date:** [July 13, 2017, 7:08pm UTC](https://discuss.elastic.co/t/groks-for-parsing-windows-and-redhat-syslogs/93071/1 "2017-07-13T19:08:07Z")

</div>

I am currently trying to parse syslog messages coming from Windows OS and Redhat. Obviously this has been done before by a lot of people. I was wondering if there was a website or if someone could point me to a location where there are some well written groks for these OS syslog messages. I can write these groks myself, but you know how the saying goes:

> "Work smarter not harder"

Thanks!

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [July 13, 2017, 7:16pm UTC](https://discuss.elastic.co/t/groks-for-parsing-windows-and-redhat-syslogs/93071/2 "2017-07-13T19:16:29Z")

</div>

Perhaps the RedHat ones match what the Logstash documentation covers.

[https://www.elastic.co/guide/en/logstash/current/config-examples.html](https://www.elastic.co/guide/en/logstash/current/config-examples.html)

---

<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:** [August 10, 2017, 7:17pm UTC](https://discuss.elastic.co/t/groks-for-parsing-windows-and-redhat-syslogs/93071/3 "2017-08-10T19:17:09Z")

</div>

Closed on August 10, 2017, 7:17pm UTC

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