Heartbeat enabled: false kills process with error

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

To follow-up here, I created this bug to track this: https://github.com/elastic/beats/issues/22665

1 Like

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