Hey, I hope you're having a great week.

We added Container Restart Notifications to help you stay informed when your containers restart unexpectedly.

Custom alerts are also coming - keep reading.

Let's talk about restarts first.

---

How It Works

Previously, we only notified you after the 11th restart, and there was no way to disable these notifications. Now you get notified right away.

Quave ONE monitors your containers and notifies you when restarts occur. This helps you catch issues like crashes or out-of-memory errors - even if the container auto-recovers.

• Get notified immediately when a container first restarts
• Receive at most one notification every 3 hours if restarts continue
• Works with both Email and Slack
• Configurable per account or per environment

Each notification includes the container name, restart count, exit code, error message (when available), and the application version.
Documentation →

---

Better Restart Tracking

We also improved how restarts are tracked:

• Restart counts are now based on actual restart events rather than Kubernetes counters
• We store up to 100 restart events per container (previously 5)
• No duplicate notifications for the same restart event

---

Managing Notifications

Restart notifications are enabled by default. To adjust:

1. Go to Account → Notifications or App Env → Notifications
2. Find Restarts
3. Toggle Email and/or Slack as needed

For a list of common exit codes, see the Troubleshooting guide.

---

Custom Alerts

We have much more coming. We're wrapping up our custom alerts feature where you can monitor your resources and receive alerts from Grafana on your email, Slack, PagerDuty, or even a custom webhook.

If you want to be our beta tester on this new feature, let us know at support@quave.cloud.

BTW, our MCP is great for debugging and understanding issues on your app or database. We'll share more content about it soon - stay tuned.