# Managing Endpoints Monitored by Heartbeat
**URL:** https://discuss.elastic.co/t/managing-endpoints-monitored-by-heartbeat/271019
**Category:** Beats
**Tags:** heartbeat
**Created:** [April 22, 2021, 8:47pm UTC](https://discuss.elastic.co/t/managing-endpoints-monitored-by-heartbeat/271019 "2021-04-22T20:47:41Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@Tim\_Mobley](https://discuss.elastic.co/u/Tim_Mobley)
#### Post date: [April 22, 2021, 8:47pm UTC](https://discuss.elastic.co/t/managing-endpoints-monitored-by-heartbeat/271019/1 "2021-04-22T20:47:41Z")
Is a more dynamic way to manage hostnames or IPs monitored by Heartbeat other than putting them in the `hosts` list in the files found in the `monitors.d` folder? There appears to be a character limit for that array, which is part of the problem. But the main difficulty is the management overhead for these lists. Can you use wildcards for IP ranges or hostnames? Can you reference a text file containing the hosts list? Or is the only option to manually type each host in the yml file? Thank you!
---
### Author:  [@Andrew\_Cholakian1](https://discuss.elastic.co/u/Andrew_Cholakian1)
#### Post date: [May 3, 2021, 8:47pm UTC](https://discuss.elastic.co/t/managing-endpoints-monitored-by-heartbeat/271019/2 "2021-05-03T20:47:46Z")
@Tim_Mobley Our current focus is on deepening the experience for our synthetic monitors rather than this particular use case. For most of our users running large numbers of monitors this problem is solved by using configuration management software like Chef or Ansible, which can let you programatically define large numbers of monitors.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [May 31, 2021, 10:48pm UTC](https://discuss.elastic.co/t/managing-endpoints-monitored-by-heartbeat/271019/3 "2021-05-31T22:48:37Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.