We expanded the number of cron jobs the bastion runs every 15 min. it now deploys a total of 3 ansible playbooks, all via cron ticked at 15min. It's blowing up the monitor every 15min and spamming slack with warnings. We should either increase the threshold for the monitor (1.5 is the load threshold now, i think), stagger out the cronjobs so they are not running at the same time, or come up with a better way to trigger things rather than cronjob (a webhook trigger for the runner)
We expanded the number of cron jobs the bastion runs every 15 min. it now deploys a total of 3 ansible playbooks, all via cron ticked at 15min. It's blowing up the monitor every 15min and spamming slack with warnings. We should either increase the threshold for the monitor (1.5 is the load threshold now, i think), stagger out the cronjobs so they are not running at the same time, or come up with a better way to trigger things rather than cronjob (a webhook trigger for the runner)