# Heartbeat enabled: false kills process with error
**URL:** https://discuss.elastic.co/t/heartbeat-enabled-false-kills-process-with-error/255900
**Category:** Beats
**Tags:** heartbeat
**Created:** [November 18, 2020, 9:08pm UTC](https://discuss.elastic.co/t/heartbeat-enabled-false-kills-process-with-error/255900 "2020-11-18T21:08:04Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@Ben\_Berg1](https://discuss.elastic.co/u/Ben_Berg1)
#### Post date: [November 18, 2020, 9:08pm UTC](https://discuss.elastic.co/t/heartbeat-enabled-false-kills-process-with-error/255900/1 "2020-11-18T21:08:04Z")
Hello,
I am running heartbeat in a docker container. I would like to conditionally enable specific monitors using the enabled configuration option on a monitor by monitor basis. It appears enabled: false results in
2020-11-18T21:03:49.998Z ERROR instance/beat.go:951 Exiting: could not create monitor: Monitor not loaded, plugin is disabled
heartbeat\_1 | Exiting: could not create monitor: Monitor not loaded, plugin is disabled
Is there a way to not run/disable a monitor without this error? My use case is I am running in multiple environments and only want certain monitors to run in production, some in staging, etc. Controlling with this boolean seemed like simple option.
Thanks!
Ben
---
### Author:  [@Andrew\_Cholakian1](https://discuss.elastic.co/u/Andrew_Cholakian1)
#### Post date: [November 18, 2020, 11:36pm UTC](https://discuss.elastic.co/t/heartbeat-enabled-false-kills-process-with-error/255900/2 "2020-11-18T23:36:30Z")
To follow-up here, I created this bug to track this: [https://github.com/elastic/beats/issues/22665](https://github.com/elastic/beats/issues/22665)
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [December 17, 2020, 1:36am UTC](https://discuss.elastic.co/t/heartbeat-enabled-false-kills-process-with-error/255900/3 "2020-12-17T01:36:41Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.