# MySQL log analysis with Filebeat Logstash and Elasticsearch

**URL:** <https://discuss.elastic.co/t/mysql-log-analysis-with-filebeat-logstash-and-elasticsearch/206576>\
**Category:** Logstash\
**Created:** [November 5, 2019, 9:47am UTC](https://discuss.elastic.co/t/mysql-log-analysis-with-filebeat-logstash-and-elasticsearch/206576 "2019-11-05T09:47:33Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Vladpov](https://avatars.discourse-cdn.com/v4/letter/v/8c91f0/32.png) [@Vladpov](https://discuss.elastic.co/u/Vladpov)\
**Post date:** [November 5, 2019, 9:47am UTC](https://discuss.elastic.co/t/mysql-log-analysis-with-filebeat-logstash-and-elasticsearch/206576/1 "2019-11-05T09:47:34Z")

</div>

Hello everyone,

I'm trying to analyze MySQL and wanted to ask what is the best way to do it? 😃

I'm trying to ship logs by using Filebeat but have some problems with GROK Patterns to parsing mysql-slow-logs in a nice way.

I just found out that it's possible to use only logstash to achieve it and take logs right form log file and filter it afterwards. So what are the advantages in using Filebeat in this case?

---

<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:** [December 3, 2019, 9:47am UTC](https://discuss.elastic.co/t/mysql-log-analysis-with-filebeat-logstash-and-elasticsearch/206576/2 "2019-12-03T09:47:36Z")

</div>

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