Every MSP has a story like this: a domain lapsed, a certificate expired, a client’s site went down over a weekend — and everybody swears they saw it in a dashboard somewhere. The problem was never a lack of data. It was that the data sat in a screen nobody was looking at when it mattered.
Weavestream’s alert system exists to close that gap. It’s a native, email-based notification layer built directly on top of the documentation you’re already keeping — expirations, domain monitoring, the audit log — so the platform tells you when something needs attention instead of waiting for you to go looking.
Five Alert Types, Each Doing One Job
Rather than one generic “notify me about stuff” toggle, Weavestream splits alerting into five independent types. You pick the ones that match what you actually want to know about, and each can have its own recipients and its own company scope.
Single expiration sends one email per matching item as it enters your configured notification window — a certificate 14 days out, a password expiring in 7. Expired items stay eligible for notification, so a scan that gets missed for some reason doesn’t mean the alert never fires.
Expiration list is the digest version: one email per calendar day listing everything inside the window that day, deduplicated so a busy week doesn’t turn into a flood of individual messages.
Website down fires when a monitored domain’s HTTP check marks it offline. Recovery and any subsequent outage each generate a fresh notification, so you’re not stuck wondering whether “down” from three days ago is the same incident or a new one.
Record created / updated / deleted hooks directly into the audit log. Configure which record types you care about — assets, articles, passwords, domains, or all of them — and which actions (created, updated, deleted or archived, or any), and you get an email whenever a matching change happens.
Password created / updated runs the same pipeline, scoped specifically to vault credentials. Since passwords in Weavestream don’t hard-delete, this type covers creation and updates only.
Expirations Pulled From Data You Already Have
The two expiration alert types don’t require a separate thing to configure — they read from expiration data already living in your documentation: domain registrar (WHOIS) expiry, TLS certificate expiry on monitored domains, a password’s expiresAt date, and any custom asset field that’s typed as DATE or DATETIME with the layout’s “is expiry” option enabled.
That last one is worth calling out. If you’ve built a custom asset layout with a warranty end date, a license renewal date, or a support contract expiry field, marking it as an expiry field means it flows straight into the same alert pipeline as certificates and passwords — no extra tooling, no separate spreadsheet of renewal dates to maintain alongside the platform.
Two Ways an Alert Actually Fires
Expiration and uptime alerts run on a scheduled scan — a background job that checks for matching conditions every five minutes by default. That interval is configurable through an environment variable, and you can turn scheduled scanning off entirely if you only want real-time alerts.
Record and password alerts work differently: they’re audit-driven. The moment a matching audit entry is written — someone updates an asset, someone creates a password — an alert job is queued immediately off the back of that event. There’s no polling delay for this category; the notification is a direct consequence of the change itself. That also means disabling the scheduled scan doesn’t touch record or password alerts — they keep firing in real time regardless.
Built-In Deduplication, So You’re Not Spammed
The fastest way to get a team to ignore alerts entirely is to send them the same warning ten times. Weavestream tracks trigger keys per alert condition so that doesn’t happen: a single-expiration alert only fires once per item (or once per day inside the window, if you’d rather get reminded), an expiration-list digest sends once per configuration per day, and a website-down alert fires once per distinct outage episode rather than once per check cycle.
Every alert send — successful or not — writes its own audit entry with the recipients and outcome, so if a notification didn’t land, that’s visible in the same place you’d look for anything else that went wrong.
Company-Scoped or Global, Your Choice
Every alert configuration can be scoped to a single company or left global. A website-down alert scoped to one client only watches that client’s monitored domains; left unscoped, it watches every domain across every tenant. This matters for MSPs running alerts on behalf of specific client relationships versus platform-wide operational alerts that your own team needs regardless of which client is affected.
Access to configure alerts is capability-gated behind ALERT_MANAGE — the same model Weavestream uses everywhere else in its access control — so turning on alerting for a team lead doesn’t require handing them broader admin rights.
No New Tool, No New Vendor
This is the part that matters most for MSPs evaluating whether to bolt on yet another monitoring product: Weavestream’s alert system isn’t a separate SaaS dashboard with its own login, its own per-seat pricing, and its own onboarding curve. It’s a feature of the platform you’re already running, reading data — expirations, domain checks, audit events — that already lives there.
Delivery runs over standard SMTP, configured once under Admin → Settings → Email, with a built-in test-send so you can confirm the pipe works before relying on it. Because it’s self-hosted, there’s no rate limit imposed by a vendor, no tiered pricing based on how many alerts you want to receive, and no risk of the notification layer disappearing because a subscription lapsed.
For MSPs who’ve had a certificate expire in the blind spot between “we track that in a spreadsheet” and “someone was supposed to check the dashboard,” the value of alerts living in the same system as the underlying record is straightforward: the notification and the context needed to act on it were never in two different places to begin with.
Getting Started
If you’re already running Weavestream, head to Admin → Alerts to create your first configuration. Start with an expiration list digest scoped globally, confirm SMTP is working with the built-in test, and expand from there into record-level or website-down alerts as you figure out what your team actually wants to be notified about.
New to Weavestream? The quickstart guide gets the full stack running with Docker Compose. Alerts work out of the box once SMTP is configured and the worker process is running — no separate monitoring service to stand up.