When something needs attention
Alerts are part of Pro and Team. What Hetzner itself reports is on every plan.
When an alert fires, Cloud Viewer opens it on the affected resource, next to the charts, log lines, jobs, checks and recent changes that explain it. You can follow that path yourself, from the notification to the change in the Hetzner Console, or hand it to a coding agent.
Where an alert shows up
Section titled “Where an alert shows up”- A push notification on every phone signed in to the team. The app asks for permission the first time you sign in to a team on Pro or Team. On iPhone, critical alerts are time-sensitive and arrive during Focus modes.
- The fleet row on the dashboard: its dot turns amber or red, and the row moves to the top. See The dashboard.
- Active alerts on the dashboard: the three most severe alerts, then a summary line with the count per severity and how many are muted. History in its header shows the last 30 days.
- The email digest and alert targets, such as a webhook or PagerDuty, if a team admin has set them up. See Send alerts where you work.
From the alert to the cause
Section titled “From the alert to the cause”-
Open the alert. Tap the notification, a row under Active alerts, or the link in the digest. The alert detail shows the description, when it started, Fired N× this week if it fired more than once in the last seven days, and the affected resource.
-
Open the resource. Tap the resource row. Its detail screen puts the alert next to the evidence:
- its firing alerts and its own Alert history, so you can see how often this happens;
- the charts, with a range picker, and on a server with the agent its real disk and RAM use;
- Checks: what the uptime checks see from outside, if the resource has any;
- Jobs: when each job last ran and succeeded. A job’s Why it failed opens the log context;
- Log context: the warning lines the server wrote in the last 72 hours, with View more for filters. See Log context;
- Recent activity: what changed on the resource at Hetzner, such as a rebuild, a resize or an attached volume.
-
Rule out Hetzner. The Hetzner status section at the bottom of the dashboard shows Hetzner’s current incidents and planned maintenance.
-
Make the change in the Hetzner Console or in your infrastructure code. Cloud Viewer is read-only. Open in Hetzner Console opens the console, which cannot be linked to a single resource: use Copy resource ID on the alert detail and paste the ID into the console’s search.
-
Watch it resolve. When the condition clears, the alert resolves on every screen, and the resolved notification replaces the firing one.
The web app has the same alert and resource screens, but no push notifications and no check or job details.
Mute an alert
Section titled “Mute an alert”Muting stops an alert’s notifications for a while: push, the email digest and alert targets. The alert stays on screen, marked as muted, and is still recorded. Any team member can mute.
On the alert detail, tap Mute notifications and choose 1 hour, 4 hours or 24 hours. While the alert is muted, the same place offers Extend mute and Unmute.
On the notification itself, long-press and choose Mute 1 hour, or View to open the alert.
On the alert detail, tap Mute notifications and choose 1 hour, 4 hours or 24 hours. While the alert is muted, the same place offers Extend mute and Unmute.
The notification itself has a Mute 1 hour action.
On the alert, choose Mute, then 1 hour, 4 hours or 1 day. While the alert is muted, Unmute ends the mute early.
Share it with a colleague
Section titled “Share it with a colleague”On iPhone and Android, Share on the alert detail sends a Markdown brief of the alert, the resource and its recent history. The web app cannot share briefs. See Hand off to a coding agent.
Resolved alerts and history
Section titled “Resolved alerts and history”A resolved alert shows when it started and when it was resolved. Alert history is kept for 90 days; History in the app shows the last 30.
Several teams
Section titled “Several teams”A phone receives alerts for every team you have signed in to on it, not only the active one. Tapping an alert from another team switches to that team. Leaving a team stops its alerts. Signing out stops all push notifications to that phone.
What needs Pro
Section titled “What needs Pro”Cloud Viewer’s alert rules, their history, push notifications, the digest and alert targets are part of Pro and Team. What Hetzner reports is on every plan, including free mode: Recent activity on a resource and Hetzner status on the dashboard. A free account’s uptime checks send no alerts.
Every rule, its threshold and how long the condition must hold: Alert rules.