### Author:  [@rohitC](https://discuss.elastic.co/u/rohitC)
#### Post date: [March 23, 2017, 12:19pm UTC](https://discuss.elastic.co/t/how-to-restart-filebeat-after-adding-a-new-prospector-to-filebeat-yml/79742/1 "2017-03-23T12:19:35Z")
I downloaded Filebeat from ([https://artifacts.elastic.co/downloads/beats/filebeat/filebeat-5.2.2-linux-x86\_64.tar.gz](https://artifacts.elastic.co/downloads/beats/filebeat/filebeat-5.2.2-linux-x86_64.tar.gz)) and extracted the tar on my Ubuntu 14.04 machine.
I run Filebeat on my Ubuntu terminal with the following command:
./filebeat -c filebeat.yml
I want to add new prospectors to filebeat.yml and then restart Filebeat. How to restart filebeat extracted from the downloaded tar? Does running the command \<./filebeat -c filebeat.yml\>
again ensure previous filebeat gets stopped and filebeat starts again from where it let off?
Thanks!
---
### Author:  [@tudor](https://discuss.elastic.co/u/tudor)
#### Post date: [March 23, 2017, 12:46pm UTC](https://discuss.elastic.co/t/how-to-restart-filebeat-after-adding-a-new-prospector-to-filebeat-yml/79742/2 "2017-03-23T12:46:37Z")
I would recommend using DEB download and the init script to start/stop/restart Filebeat:
```auto
sudo /etc/initi.d/filebeat start
sudo /etc/initi.d/filebeat stop
sudo /etc/initi.d/filebeat restart
```
If you don't want to use the init script, you need to kill the old instance, before starting the new one. You can do that by pressing Control-C in the console, or by using the `kill ` command.
---
### Author:  [@rohitC](https://discuss.elastic.co/u/rohitC)
#### Post date: [March 23, 2017, 1:37pm UTC](https://discuss.elastic.co/t/how-to-restart-filebeat-after-adding-a-new-prospector-to-filebeat-yml/79742/3 "2017-03-23T13:37:37Z")
Thanks for your response @tudor . I am concerned about my access rights to /etc directory. So I would like to extract the tar in one of my directories and then execute Filebeat. Also, I want to do restart Filebeat without being concerned about killing existing Filebeat process(the way it happens in sudo /etc/init.d/filebeat restart).
Just to confirm, I tried running command \<./filebeat -c filebeat.yml\> every time I wanted to add a new prospector to filebeat.yml. When I checked running processes using command (ps -A) on my system after executing \<./filebeat -c filebeat.yml\> n times, I see n filebeat processes running.
Do you see any scope of this restart functionality be taken as an enhancement in Filebeat?
---
### Author:  [@tudor](https://discuss.elastic.co/u/tudor)
#### Post date: [March 24, 2017, 11:09am UTC](https://discuss.elastic.co/t/how-to-restart-filebeat-after-adding-a-new-prospector-to-filebeat-yml/79742/4 "2017-03-24T11:09:25Z")
We do not plan a restarting functionality in Filebeat itself, because we see this as something that needs to happen outside of the process, but we do plan to release a configuration reloading feature. This means that you will be able to add a new prospector to an existing Filebeat instance by dropping a new file in a folder: [https://www.elastic.co/guide/en/beats/filebeat/master/filebeat-configuration-reloading.html](https://www.elastic.co/guide/en/beats/filebeat/master/filebeat-configuration-reloading.html)
---
### Author:  [@rohitC](https://discuss.elastic.co/u/rohitC)
#### Post date: [March 24, 2017, 12:05pm UTC](https://discuss.elastic.co/t/how-to-restart-filebeat-after-adding-a-new-prospector-to-filebeat-yml/79742/5 "2017-03-24T12:05:26Z")
Thanks! This will be a useful feature. Any idea, when this feature is expected to be released?
---
### Author:  [@tudor](https://discuss.elastic.co/u/tudor)
#### Post date: [March 24, 2017, 12:37pm UTC](https://discuss.elastic.co/t/how-to-restart-filebeat-after-adding-a-new-prospector-to-filebeat-yml/79742/6 "2017-03-24T12:37:59Z")
It's going to be released as experimental in 5.3, which might show up as early as next week. It's experimental, though.
---
### Author:  [@Draekane](https://discuss.elastic.co/u/Draekane)
#### Post date: [April 11, 2017, 3:59pm UTC](https://discuss.elastic.co/t/how-to-restart-filebeat-after-adding-a-new-prospector-to-filebeat-yml/79742/7 "2017-04-11T15:59:57Z")
Two questions: Is this currently IN 5.3 as experimental? And if so, how do we actually need to access it? Does the whole new file need to be dropped in / replace the existing config yml? We are looking at setting up CI/CD from a repo to change things like add a new Prospector, and this is exactly what we are needing... (and I think we are looking at or possibly already working with 5.3)
---
### Author:  [@ruflin](https://discuss.elastic.co/u/ruflin)
#### Post date: [April 13, 2017, 1:11pm UTC](https://discuss.elastic.co/t/how-to-restart-filebeat-after-adding-a-new-prospector-to-filebeat-yml/79742/8 "2017-04-13T13:11:02Z")
It is in 5.3. Check the doc link tudor posted above: [https://www.elastic.co/guide/en/beats/filebeat/master/filebeat-configuration-reloading.html](https://www.elastic.co/guide/en/beats/filebeat/master/filebeat-configuration-reloading.html)
It works very similar to a conf.d directory.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [May 11, 2017, 1:19pm UTC](https://discuss.elastic.co/t/how-to-restart-filebeat-after-adding-a-new-prospector-to-filebeat-yml/79742/9 "2017-05-11T13:19:05Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.