Introducing  Notification Service in Cove – Your “Set It and Forget It” Safety Net for Backups and More

General Availability — May 29, 2025

Partner: “Every morning I waste time scrolling through all my different dashboards and I still miss stuff.”

Cove: “Set up alerts in as little as 90 seconds – you’ll only hear from us when something actually fails.”

The Problem: Too Many Solutions, Too Many Dashboards

Some partners can spend up to four hours every week looking through all their dashboards to spot failures or errors.

For MSPs, that’s four hours of non-billable time every single week – and it still relies on a human catching the problem in time.

The Cure: Native, Event-based Notifications

“Four-six-eight hours a week staring at dashboards is hours you’re not serving customers. Notification Service gives that time back.” – Ihor Pietukhov, Product Manager

Cove’s new Notification Service watches every protected device – on-prem servers and workstations plus Microsoft 365 tenants – with no exclusions.

The moment a backup Fails or Completes with Errors, Cove emails the right people so they can act before data loss or SLA breaches hit.

What You Get on Day One

• Status coverage: Failed and Completed with Errors
• Scope: every on-prem device and M365 domain you protect
• Roles & permissions: SuperUser/Admin can create rules; technicians get alerts, not admin rights
• Zero extra cost: included in every Cove license

Set-up takes ~90 seconds

1. Go to Management → Notifications.
2. Click Add Notification.
3. Pick customer → device type → status.
4. Choose internal recipients.
5. Done.

Preview feedback we already baked in

• Server / Workstation split – create separate rules for your servers and workstations.
• Roadmap reshuffle – external-recipient support moved up because you asked for it.

Under the Hood (A Taste of the Tech)

Notification service is based on microservices and event-based architecture. It consists of several components communicating with each other using events making it extensible, scalable and resilient.

The central part of Notification Service is Cove distributed event system. It is scalable and resilient by design. It can be extended on demand and independently from any other components of the product. So, whenever Cove starts producing a new event, it can be easily hooked up by Notification Service and provided as an option for Notification rule configuration.

Template system is a component of Notification Service that is responsible for generating content for notifications. It is designed with customization and extensibility in mind so that new templates and customizations could be added fast and easily. Currently, only HTML content is supported with limited customization, JSON payload is planned for automated flows using native integrations and webhooks.

Delivery system is responsible for actual delivery of notifications. It is designed to support various delivery channels. Email channel is the first one supported, then we are going to add channels for native API integrations and webhooks. This component is naturally designed to be scalable and fault tolerant.

Notification system is another component that is created for easy, but powerful fine-tuning of Notification Configurations allowing filtering by an arbitrary event field or adding additional conditions when notification must be sent.

Such separation lets us ship new event types and channels fast – without touching the core pipeline.

What’s Coming Next

“Notification Service turns data protection from something you check into something that checks on you. This is step one of a bigger vision: Cove as the silent guardian that only speaks when action matters.” – Stefan Voss, VP of Product Management

Take Action Today

1. Create one notification rule for your most important customer.
2. Delete a legacy script or manual check and reclaim those hours.
3. Tell us what else you need – your feedback already shapes the roadmap.

Stop staring at dashboards. Let Cove tap you on the shoulder only when something goes wrong – starting May 29.