Skip to main content

Notifications

Notifications send operational summaries without changing whether work runs. They are separate from Spend Controls, which can keep queued deployments from dispatching.

Today, Anycloud supports a daily Slack digest. The local API reads activity from ~/.anycloud/api.db, reports Jobs and Servers in separate sections, and posts directly from your machine to the webhook you configure.

Enable Slack​

Create a Slack incoming webhook for the destination channel, then run:

anycloud notifications enable slack \
  --webhook https://hooks.slack.com/services/T.../B.../...

The CLI validates the URL and posts a test message before saving it.

anycloud notifications status
anycloud notifications test slack
anycloud notifications disable slack

Digest timing​

The local API checks every 15 minutes. Once per UTC day after midnight, it summarizes the previous UTC calendar day when there was relevant activity. The first check after enabling establishes a starting point rather than sending an incomplete historical digest.

The digest starts with contributing users and host-wide compute spend. It then reports Jobs and Servers separately, with compute spend and provisioned VM hours and attempts for each:

  • Jobs report initial submissions, resubmissions, terminal results, preemptions, and median duration.
  • Servers use server-specific launch wording and omit median duration because they are long-running.

Inactive sections and lines with a zero count are omitted.

Submission, VM usage, resubmission, and terminal-state counts independently use the day named in the digest. A deployment can therefore be submitted one day, resubmitted another, and finish later.

Waiting-on-spend-cap alerts are also sent when a Spend Control begins blocking queued work, then at most once every six hours while it remains blocked.

Local storage​

Configuration is saved at ~/.anycloud/notifications.json with mode 0600. ~/.anycloud/notifications-digest-last-posted records the latest reported date, preventing an API restart from posting the same digest twice.

Slack is currently the only channel. See notifications reference for exact syntax.