# Refreshing configuration
**URL:** https://discuss.elastic.co/t/refreshing-configuration/139830
**Category:** Beats
**Tags:** heartbeat
**Created:** [July 12, 2018, 8:09pm UTC](https://discuss.elastic.co/t/refreshing-configuration/139830 "2018-07-12T20:09:39Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@joaociocca](https://discuss.elastic.co/u/joaociocca)
#### Post date: [July 12, 2018, 8:09pm UTC](https://discuss.elastic.co/t/refreshing-configuration/139830/1 "2018-07-12T20:09:40Z")
I've killed HB, made changes for heartbeat.monitors on my heartbeat.yml config file, and restarted HB... but it keeps monitoring the old configuration? Changes include commenting out a full type and changing tags on other types.
Is there a way to force this refresh?
---
### Author:  [@adrisr](https://discuss.elastic.co/u/adrisr)
#### Post date: [July 12, 2018, 10:36pm UTC](https://discuss.elastic.co/t/refreshing-configuration/139830/2 "2018-07-12T22:36:41Z")
There are no additional steps other than restarting the Beat.
A few things that could be causing this:
- You are looking at old events generated with the old configuration.
- You are modifying the wrong config file. Look for `Config path:` in the log.
- It restarted automatically shortly after you killed it and before any changes to the configuration.
---
### Author:  [@joaociocca](https://discuss.elastic.co/u/joaociocca)
#### Post date: [July 13, 2018, 4:48pm UTC](https://discuss.elastic.co/t/refreshing-configuration/139830/3 "2018-07-13T16:48:27Z")
for the one I was messing around when I posted this, I think it was the first option. After a while, new data started arriving as supposed!
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [August 10, 2018, 4:48pm UTC](https://discuss.elastic.co/t/refreshing-configuration/139830/4 "2018-08-10T16:48:33Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.