# Running slow log for long periods of times

**URL:** <https://discuss.elastic.co/t/running-slow-log-for-long-periods-of-times/158098>\
**Category:** Elasticsearch\
**Created:** [November 25, 2018, 6:12pm UTC](https://discuss.elastic.co/t/running-slow-log-for-long-periods-of-times/158098 "2018-11-25T18:12:22Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jacques\_du\_Plessis](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jacques_du_plessis/32/35413_2.png) [@Jacques\_du\_Plessis](https://discuss.elastic.co/u/Jacques_du_Plessis)\
**Post date:** [November 25, 2018, 6:12pm UTC](https://discuss.elastic.co/t/running-slow-log-for-long-periods-of-times/158098/1 "2018-11-25T18:12:22Z")

</div>

I enabled slow, for debugging purposes, What will the impact be if I run it for long periods of times.  
Will there be a performance hit?

Also, what is the best practice in regards to the log files are they basically only for debugging or can I use them for metrics as well. And if they are what will be the best way to index them from the log file.  
I was thinking of just using FileBeats.

But would there be any value to doing that? What are other companies doing.

---

<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 23, 2018, 6:12pm UTC](https://discuss.elastic.co/t/running-slow-log-for-long-periods-of-times/158098/2 "2018-12-23T18:12:22Z")

</div>

Closed on December 23, 2018, 6:12pm UTC

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