# MsSQL Log beat **URL:** \ **Category:** Beats\ **Created:** [June 13, 2018, 4:24pm UTC](https://discuss.elastic.co/t/mssql-log-beat/135765 "2018-06-13T16:24:24Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![PandKing](https://avatars.discourse-cdn.com/v4/letter/p/258eb7/32.png) [@PandKing](https://discuss.elastic.co/u/PandKing)\ **Post date:** [June 13, 2018, 4:24pm UTC](https://discuss.elastic.co/t/mssql-log-beat/135765/1 "2018-06-13T16:24:25Z")
Hi, Is there a way to pull in MsSQL logs into elastic ? Some filebeat plugin... maybe? Looked across the beats forum didn't see any real discussions on the topic. Didn't see anything specific in GitHub. Thanks Scot ---
**Author:** ![jsoriano](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jsoriano/32/27920_2.png) [@jsoriano](https://discuss.elastic.co/u/jsoriano)\ **Post date:** [June 14, 2018, 7:05am UTC](https://discuss.elastic.co/t/mssql-log-beat/135765/2 "2018-06-14T07:05:40Z")
Hi @PandKing, We don't have a MSSQL module in filebeat yet, but you can configure an [input](https://www.elastic.co/guide/en/beats/filebeat/6.3/configuration-filebeat-options.html) with the log files. To parse them you'd need to use an [ingest node](https://www.elastic.co/guide/en/beats/filebeat/6.3/configuring-ingest-node.html) or [logstash](https://www.elastic.co/guide/en/logstash/6.3/advanced-pipeline.html). Feel free to [open an issue](https://github.com/elastic/beats/issues/new) in github to request a MSSQL module 🙂 ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 12, 2018, 9:05am UTC](https://discuss.elastic.co/t/mssql-log-beat/135765/3 "2018-07-12T09:05:42Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.