Snooze, quiet hours and the digest

A phone that buzzes at three in the morning about something that can wait gets muted, and then misses the one thing that cannot. How to hold the alerts you do not need right now, and read what the night did over breakfast.

On this page

Which one you want #

You want Use It lasts
Nothing about one box or one environment for a while Snooze Until a time you pick, at most a week ahead
Only what cannot wait, at night Quiet hours A daily window
One message that counts what happened The morning digest Once a day
No "gone dark" while you reboot a box A maintenance pause, from the box At most a day

The first three are set in the console and are on every plan. The fourth is a command on the box, and it works differently: not the maintenance pause says how.

None of them changes what Watch shows. A snoozed box that goes down is still down in the inbox, in the same place. They change what reaches your phone.

Held means not sent, then or later #

One rule covers snooze and quiet hours. An alert that fires while either applies is held: Watch writes it to the alert history, marks why, and sends it nowhere. It is never sent later. Not when the snooze ends, not when quiet hours end, and not if the thing is still wrong then.

That is deliberate. An alert that arrives five hours late tells you about a moment that has passed, and reads as if it were now. What is true now is in the inbox. What you missed is in the history and in the digest.

Three things follow from the rule:

  • The notice is held too. A box that goes down while it is snoozed sends no "down". When it comes back it sends no "recovered" either, even if the snooze has ended by then. You are not told about the end of something you were never told about.
  • A snooze that ends says nothing. If the box is still dark when its snooze runs out, no alert is sent for it. The alert fired once, when the box went down, and that one was held.
  • Held alerts are counted. The next digest says how many alerts were held, and counts each in its own line as well.

The console's alert history shows each held alert with one of three lines:

The history says Because
Not sent: snoozed. Its machine or its environment was snoozed when it fired.
Not sent: quiet hours. It fired inside your quiet hours and was not urgent, or you hold urgent alerts too.
Not sent: the alert it follows was not sent. It is the notice for an alert that was itself held.

Snooze #

You have paused a client's project for the week, or a box is waiting on a part and you know it is dark. You do not need to hear about it again.

Open the machine or the environment in the console and choose how long under Snooze alerts: 1 hour, 4 hours, 1 day or 1 week. The page then reads "Snoozed until Sat 14:30", with End snooze beside it, and its rows in the inbox read:

On a snoozed row
Snoozed until 14:30. No alerts.

What a snooze covers depends on what you snoozed:

You snooze Watch holds
An environment Every alert about that environment and its sessions.
A machine Every alert about the machine, every environment on it, and their sessions.

Snoozing an environment does not cover its machine. If the box goes dark, loses mains power or fills its disk, you hear about that. Snooze the machine for those.

A snooze ends by itself at the time you chose, and at most a week ahead. Snoozing again replaces the time. End snooze ends it now. Where an environment and its machine are both snoozed, the environment shows the later of the two times, and ending the environment's own snooze leaves it snoozed until the machine's runs out.

A snooze holds alerts and does nothing else. Statuses change as they always do, the inbox sorts as it always does, and nothing on the box is touched.

Quiet hours #

Most of what Watch sends can wait until morning. A session paused on a usage limit will still be paused at breakfast. An agent waiting on you at 02:00 is a night's work lost if nobody answers.

Quiet hours are a daily window in which Watch sends only what is urgent. Set them in the console, on the alerts page under When alerts are sent: a time zone, and Quiet hours from one time to another. A window that ends before it starts crosses midnight, so 22:00 to 07:00 is nine hours overnight. The same time twice is refused.

During the window:

Alert What happens
Urgent: a box gone dark, an agent server down or restarting, a box on battery, a disk filling, a session waiting, failed, stuck or signed out Sent, as at any other time.
Ordinary: a session paused on a usage limit, a login that expires soon, a session that ended with unsaved work, and every "recovered", "settled", "moved on" and "mains power back" Held, and counted in the next digest.

So during quiet hours you hear that a box went down, and you do not hear that it came back. The notice is ordinary. The digest counts it among the held, and the inbox shows the box online.

An alert is judged at the moment it fires. One that fires a minute before the window closes is held, and is not sent when the window closes.

Hold urgent alerts too holds everything.

Quiet hours hold alerts with nowhere to count them unless you also set a digest. Without one, the held alerts are in the history and nowhere else.

The morning digest #

A quiet night is not always a good one. The digest is one message, at a time you choose, that counts what happened since the last one.

Set it on the alerts page, under When alerts are sent: Morning digest at a time. It goes to every destination that takes your alerts, and never to a second contact. Watch calls up to 40 addresses a minute, so an account with more than that hears at the rest over the minutes that follow.

A digest
Since 08:00: 7 finished, 4 to look at

7 sessions finished. 3 pull requests opened. 2 waited on you. 1 paused on a usage limit. 1 failed. 4 alerts were held.

The first line is the title. "To look at" adds up everything that wanted someone: sessions that waited, paused on a limit, lost their login, failed or got stuck, and machines that went dark. The body has one sentence for each count that is not zero:

The digest says It counts
7 sessions finished Sessions that came to rest from working: they finished a turn, or ended in the middle of one. Each is counted once, whatever it has done since.
3 pull requests opened Pull requests Watch first heard of from what a session left.
2 waited on you Sessions that waited past the deadline.
1 paused on a usage limit Sessions that hit their vendor's limit.
1 login expired Sessions that stopped because the agent was signed out.
1 failed Sessions that stopped with any other error.
1 got stuck Sessions Watch called stuck.
1 machine went dark Times a machine went down.
4 alerts were held Alerts that fired and were not sent, whatever the reason.

Four things to know when you read one:

  • It counts what happened, not what is true now. A session that waited at 02:00 and was answered at 02:30 is still one that waited. The inbox has what is true now.
  • It counts held alerts where they belong. A session that failed while its environment was snoozed is in "failed" and in "alerts were held".
  • It covers the time since the last one. That is a day, unless you moved the time. The first digest covers the 24 hours before it, and so does the first after you switch the digest off and on again.
  • A session finishes once. A session that stopped at 02:00 and is closed the next afternoon finished at 02:00. Closing it is not finishing again, and nor is the agent asking a minute later what it should do next.
  • It leaves out what your plan hides. An environment beyond your plan's limit is not counted, as it is not alerted on.

On a day with every count at zero, nothing is sent. Switch on Send it even when nothing happened if you would rather have the proof that Watch looked:

An empty digest
Nothing to report since 08:00

No session finished, waited, failed or got stuck, and no machine went dark.

The digest is not an alert. It is in no alert history, it cannot be acknowledged, and nothing is held or sent on because of it. The console keeps the latest one and shows a line for it, such as "Last digest sent 08:00 to 1 destination." It arrives at ordinary priority with the tag sunrise. What a webhook receives has the headers.

"Sessions finished" needs nothing from the box beyond what it already sends. "Pull requests opened" comes from the count a box makes when a session stops, so it covers sessions in a nucleus, on a box whose daemon reports what a session left, with repos on GitHub.

The time zone #

One setting, Time zone, on the same part of the alerts page. It is the name of a zone such as Europe/London, and it is UTC until you set it. Three things use it:

  • Quiet hours start and end at those times in that zone.
  • The digest is sent at that time in that zone, within a minute or two.
  • Every time written in an alert or a digest is in that zone: the hour, the minute and the zone's short name, as in "03:10 UTC".

It follows daylight saving. Quiet hours from 22:00 are from 22:00 on your wall all year, and the digest does not move by an hour twice a year.

Two places do not use it. The console shows times in the time zone of the device you are reading it on. And the on-box notifier writes its times in UTC, because the box does not know your account's settings and is speaking when Watch cannot.

Not the maintenance pause #

A maintenance pause and a snooze both keep your phone quiet about a box. They are for different moments, and they treat a held alert in opposite ways.

Snooze Maintenance pause
Set from The console, for a machine or an environment The box, with nucleated pause
Covers Every alert about it Machine down and environment down, and nothing else
An alert that fires meanwhile Is held, and never sent Is put off, and sent at the end if the box is still dark
Longest A week A day

Use the pause for work you are doing on purpose and expect to finish: a reboot, a move, a swapped part. If it goes wrong and the box never comes back, the pause tells you when it ends. Use a snooze for something you already know about and do not want to hear about again. It never tells you anything.

When both apply to a machine, the pause acts first. An alert the pause releases at its end is then treated like any other: it is held if the machine is snoozed at that moment, or if your quiet hours are running and you hold urgent alerts too.

What none of them does #

Snooze, quiet hours and the digest are about what is sent to you. They never reach the box.

  • No agent is touched. Nothing here stops, pauses or messages a session. Watch has no way to.
  • Nothing is hidden from the inbox. Every status still changes and still sorts where it would.
  • Nothing is lost. A held alert is in the history for as long as your plan keeps history, marked with why it was not sent.
  • Nothing new leaves the box. The digest is built from counts Watch already has.