Schedule playbook for multiple databases #145
Description
Right now, a playbook is scheduled for an individual database. This is limiting for a number of reasons. You automatically do not have visibility into new DB's added, you could be monitoring DB's that don't exist and changing schedules can be annoying if you have to do it for multiple DB's. I'd like to see the ability to create a playbook that allows you to select multiple DB's instead of manually scheduling each one, and I'd like the option to monitor the entire cluster to dynamically capture any new / removed databases.