Managing Endpoints Monitored by Heartbeat

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!

@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.