Dev and QA do not need to run at three in the morning. Everybody agrees, and nobody powers them off, because the person who would do it went home too, and a cron on someone's laptop is not a process. The one time it does run, nobody can say which VMs it stopped or why one came back.
Control Cloud schedules power resources off and on at set times, on a cron expression in the timezone you pick, and every run lands in the audit log: when it fired, what matched, what failed. Recorded on a demo organization:
The same clip, with the night cost next to it, is on the docs page.
What powers your dev VMs off tonight, and could you tell tomorrow what it did?
Top comments (0)