Resource groups

A resource group is a named bundle of resources you want to manage as one unit; a dev cluster, a staging stack, a customer’s tenant. Once you’ve grouped them, you can attach a single schedule, run bulk start/stop, and see cost rolled up at the group level.

The Groups page; related resources bundled per team, each with a resource count and budget rollup.

When to use a group

Use groups when the same lifecycle policy applies to everything inside. If your “staging” environment is twelve resources that should all sleep on weeknights and weekends, that’s a group. If three of the twelve need to stay on, they belong to a different group (or to no group at all).

Create a group

1. Open Groups → New group

   Give it a name and an optional description. The description shows up in the group list, so use it to explain why this group exists; future-you will thank you.

2. Add resources

   Search by name or UID, or filter by type and region. Tick the resources you want and click Add. Bulk selection is supported.

3. (Optional) Attach a schedule

   Pick an existing schedule or create a new one. All current and future members will follow it. See Schedules for cron syntax.

Sequenced execution

Some stacks have dependencies; databases need to be up before app servers; app servers need to be up before workers. ZopNight runs group start/stop in a configurable order. See Scheduling for the same ordering model as it applies to schedules.

Mode	Behaviour
Auto (default)	Storage first, compute second, applications third. Works for most stacks.
Custom	You define the exact order. Use this when auto-ordering doesn’t match your dependency graph.

You can also set a delay between resources in minutes. A 2-minute delay between a database start and an app server start gives the DB time to accept connections before the app tries to use it.

Bulk start and stop

Group → Start all or Stop all runs the action across every member through the worker pool. Four workers run in parallel, ordering and delays are honoured, and a single banner shows progress so you don’t have to refresh.

Budgets per group

Each group can have a monthly budget. ZopNight tracks live spend against it from your cost records (no separate counter to keep in sync; spend is computed on every read).

Budget alerts go through the notification service. Slack, Teams, Google Chat, or webhook.

Overrides on a group

Just like resources, groups can be overridden ON or OFF for a window. Setting an override at the group level applies to every member. Useful for “everyone stays up tonight, we’re cutting a release.”

See Overrides for the full behaviour.

Deleting a group

Deleting a group does not delete its resources: the resources keep running and stay in the inventory. The group’s schedule attachment, sequencing, and budget go away.

Group delete is a soft delete. You won’t see deleted groups in the list, but the audit log keeps the trail.