# The live\_reloading wouldn't caused the original prospector stopped?

**URL:** <https://discuss.elastic.co/t/the-live-reloading-wouldnt-caused-the-original-prospector-stopped/128105>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [April 16, 2018, 6:03am UTC](https://discuss.elastic.co/t/the-live-reloading-wouldnt-caused-the-original-prospector-stopped/128105 "2018-04-16T06:03:43Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![jackyshen](https://avatars.discourse-cdn.com/v4/letter/j/85f322/32.png) [@jackyshen](https://discuss.elastic.co/u/jackyshen)\
**Post date:** [April 16, 2018, 6:03am UTC](https://discuss.elastic.co/t/the-live-reloading-wouldnt-caused-the-original-prospector-stopped/128105/1 "2018-04-16T06:03:44Z")

</div>

I found the information about filebeat live\_reloading in the following URL:  
[https://www.elastic.co/guide/en/beats/filebeat/current/\_live\_reloading.html](https://www.elastic.co/guide/en/beats/filebeat/current/_live_reloading.html)

And it states "When the files found by the Glob change, new prospectors and/or modules are started and stopped according to changes in the configuration files."

What's meaning? suppose I started a filebeat instance, and there is just one log file to watch, so there is one original prospector would be created and running, then I changed the config file, so based on description in the URL, the filbeat would create a new prospector , right ? So there are two prospectors running and dealing with the same log file in the same time ? The original prospector wouldn't be stopped automatically when the new prospector created?

---

<div class="post-metadata">

**Author:** ![exekias](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/exekias/32/28718_2.png) [@exekias](https://discuss.elastic.co/u/exekias)\
**Post date:** [April 16, 2018, 8:51am UTC](https://discuss.elastic.co/t/the-live-reloading-wouldnt-caused-the-original-prospector-stopped/128105/2 "2018-04-16T08:51:47Z")

</div>

Hi @jackyshen,

If you update the existing one Filebeat will detect the change and stop the existing prospector to create a one with the new config.

If you want to launch a new prospector you will need to create a new config file in the config reloading folder.

Best regards

---

<div class="post-metadata">

**Author:** ![jackyshen](https://avatars.discourse-cdn.com/v4/letter/j/85f322/32.png) [@jackyshen](https://discuss.elastic.co/u/jackyshen)\
**Post date:** [April 17, 2018, 3:39am UTC](https://discuss.elastic.co/t/the-live-reloading-wouldnt-caused-the-original-prospector-stopped/128105/3 "2018-04-17T03:39:53Z")

</div>

Got it,and thanks

---

<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:** [May 15, 2018, 3:39am UTC](https://discuss.elastic.co/t/the-live-reloading-wouldnt-caused-the-original-prospector-stopped/128105/4 "2018-05-15T03:39:55Z")

</div>

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