Skip to content

Notifications & integrations

Notifications fan out platform events — service incidents, spend alerts, role changes, audit anomalies — to the people and systems that need to know. Configure them per-user (personal preferences) or org-wide (default channels).

Overview

Notifications settings Notifications page. Channels on the left, event-type-to-channel matrix on the right.

Three layers of configuration:

Layer Set in Affects
Personal User menu → Account → Notifications Where you get notified
Project Project Settings → Notifications Per-project events (defaults inherited from org)
Org Org Settings → Notifications Org-wide events + default for all projects

Personal preferences override project defaults; project settings override org defaults.

Channels

Channel Latency Best for
Email seconds — minutes Default for everything
Webhook seconds Custom integrations
Slack (via webhook) seconds Engineering / NOC channels
Microsoft Teams (via webhook) seconds Same
PagerDuty seconds On-call escalation
Opsgenie seconds Same
ServiceNow seconds — minutes ITSM ticket auto-creation
SMS (preview) seconds Critical-only, optional add-on
Mobile push (roadmap) seconds Cloud Digit mobile app

Event categories

Category Examples
Authentication New sign-in from new IP, failed sign-in burst, password change, MFA reset
Authorization Role changed, member added/removed, token issued/revoked, custom-role updated
Resource lifecycle VM created/deleted, volume attached/detached, cluster up/down
Resource health VM in Error, volume detach failed, K8s node NotReady
Spend Budget at 80% / 95% / 100%, anomaly detected, top-up cleared
Service health Cloud Digit incidents (degraded / outage), maintenance windows
Audit anomaly Unusual API call patterns, off-network access, mass-delete events
Compliance Object Lock retention near expiry, audit pack ready, KYC re-verification due

Administration

Org-wide defaults

Org Settings → Notifications → Default recipients:

Event class Default recipients
Billing org.billing.dl@your-domain
Security org.security.dl@your-domain
Compliance org.compliance.dl@your-domain
Operations org.ops.dl@your-domain
User-facing announcements org.admin.dl@your-domain

These mailing-list addresses live at your mail server, not Cloud Digit. We just push to them.

Quotas

Resource Default per org Cap
Webhook destinations 50 500
PagerDuty / Opsgenie services 25 100
Email recipients per event 100 500
Notifications per minute (rate limit) 1,000 bumpable

Operation

Adding a webhook

Notifications → Channels → + Add → Webhook:

  1. Name — e.g. slack-noc
  2. URL — your endpoint
  3. Method — POST (default) / PUT
  4. Headers — optional auth (X-API-Key: ..., etc.)
  5. Format — JSON (default) / CEF / Jinja2 custom template
  6. Retries — exponential backoff on 5xx (default on)
  7. Test — Cloud Digit sends a synthetic event to confirm

Once added, route events to it from the Routing matrix.

Slack / Teams integration

These are technically webhooks but Cloud Digit ships pre-built templates that render nicely in Slack / Teams:

  1. In Slack/Teams, create an incoming webhook for the target channel (workspace admin in Slack, channel owner in Teams)
  2. Copy the webhook URL
  3. In Cloud Digit, Notifications → Channels → + Add → Slack (or Teams) — paste the URL
  4. Test → confirms a friendly message lands in the channel
  5. Route events from the Routing matrix

PagerDuty / Opsgenie

For on-call escalation:

  1. Notifications → Channels → + Add → PagerDuty (or Opsgenie)
  2. Paste the integration key from your service
  3. Test → Cloud Digit creates a synthetic incident at the destination
  4. Route only critical / urgent events here (avoid alert fatigue)

Routing matrix

The matrix is the heart of notifications. Rows = event types, columns = channels. Tick the cells that should fire.

Common patterns:

Event Email Webhook Slack PagerDuty SMS
Sign-in from new IP ✓
Failed-sign-in burst (≥ 10/min from one IP) ✓ ✓ ✓
VM in Error state ✓ ✓
Spend at 80% budget ✓
Spend at 100% budget ✓ ✓ ✓
Cloud Digit P1 in your region ✓ ✓ ✓ ✓ ✓
Audit anomaly ✓ ✓ ✓ (severity-dep)
KYC re-verification due ✓

Quiet hours

For low-priority events, set per-channel quiet hours (e.g. "no Slack pings between 23:00 and 07:00"). Critical events override quiet hours — that's by design.

Per-user preferences

Each user can opt out of specific event types or downgrade to digest mode (a daily summary instead of per-event push). Settings → Notifications under User menu → Account.

Operating-tier integrations

If you've subscribed to 24/7 Managed Monitoring, the Cloud Digit NOC is automatically subscribed to your critical events — they triage and escalate to you per your runbook.

If you've subscribed to Managed SIEM, audit-anomaly notifications can be routed via SIEM (with full Sigma-rule filtering) instead of (or in addition to) the platform-native notification channels.

Troubleshooting

Symptom Likely cause Fix
Webhook test fails with timeout Endpoint unreachable from Cloud Digit's egress Confirm endpoint is internet-accessible; check firewall
Slack messages malformed Old webhook URL with deprecated format Re-issue the Slack webhook
PagerDuty creates many duplicate incidents Dedup-key not set in Cloud Digit's payload Switch the channel to "PagerDuty Events API v2" mode (default; manual override possible)
User not receiving emails despite subscription Org-level recipient mailing list excludes them; or their account has email disabled Check both org-level routing AND user's personal preferences
Too many alerts during incident Storm-control hadn't kicked in Storm control is on by default; review the rate-limit settings
Audit-anomaly alerts noisy Default thresholds too tight for your workload Tune via SIEM Sigma rules, or via the built-in anomaly threshold knob