Events and Notifications

Datafi generates events for significant platform activity -- data source connections, policy violations, query failures, user actions, and more. The Events and Notifications settings let you decide which events trigger notifications, how they are prioritized, and where they are delivered.

---

Event Configuration

Events are organized by category. You enable or disable notifications for each event type independently.

Category	Example Events
Data Sources	Connection established, connection lost, schema change detected, sync completed.
Queries	Query failed, query timeout, long-running query threshold exceeded.
Users	User invited, user accepted invitation, user deactivated, role changed.
Policies	Policy created, policy violation detected, policy updated.
AI/ML	Agent triggered, agent completed, model error, embedding re-index started.
System	Scheduled maintenance, platform update available, storage quota warning.

To configure events:

1. Navigate to Administration > Events.
2. Browse or search the event catalog by category.
3. Toggle notifications on or off for each event type.
4. Click Save.

tip

Start by enabling notifications for high-impact events only -- such as connection failures and policy violations -- and expand coverage as your team becomes comfortable with the notification volume.

---

Notification Types

Datafi supports multiple notification channels. You can route different event categories to different channels based on urgency and audience.

Channel	Description	Configuration Required
In-App	Notifications appear in the bell icon within the Datafi interface.	None. Enabled by default.
Email	Notifications are sent to user email addresses or distribution lists.	SMTP configuration (see below).
Webhook	A JSON payload is sent to an external URL for integration with tools like Slack, PagerDuty, or custom systems.	Webhook endpoint URL.

Channel Routing

You map event categories to channels in the Routing Rules section.

# Example routing configuration
routing:
  data_sources:
    connection_lost:
      channels: [in_app, email, webhook]
      priority: critical
    schema_change:
      channels: [in_app]
      priority: info
  queries:
    query_failed:
      channels: [in_app, email]
      priority: high
  policies:
    violation_detected:
      channels: [in_app, email, webhook]
      priority: critical

---

Notification Priorities

Each event is assigned a priority level that determines its visual treatment, delivery urgency, and default routing behavior.

Priority	Badge Color	Delivery	Description
Critical	Red	Immediate	Service-affecting events that require prompt attention.
High	Orange	Immediate	Important events that may impact operations.
Medium	Yellow	Batched (5 min)	Noteworthy events that do not require immediate action.
Low	Blue	Batched (15 min)	Informational events for awareness.
Info	Gray	Batched (1 hr)	Routine activity logs with no action required.

You can override the default priority for any event type in the event configuration panel. Batched notifications are aggregated into a single digest to reduce noise.

note

Critical and High priority notifications always bypass batching and are delivered immediately regardless of digest settings.

---

Email Settings

To enable email notifications, you must configure an SMTP connection. Navigate to Administration > Events > Email Settings.

Setting	Description	Example
SMTP Host	The hostname of your mail server.	smtp.example.com
SMTP Port	The port used by the mail server.	587
Encryption	The encryption protocol.	STARTTLS or SSL/TLS
Username	The SMTP authentication username.	[email protected]
Password	The SMTP authentication password.	(stored encrypted)
From Address	The sender address shown on outgoing emails.	[email protected]
From Name	The sender display name.	Datafi Platform

After entering your SMTP details:

1. Click Test Connection to verify the server is reachable.
2. Click Send Test Email to confirm end-to-end delivery.
3. Click Save to activate email notifications.

warning

If your mail server enforces IP allowlisting, add the Datafi platform IP addresses to the allowlist. Contact your Datafi administrator or check the deployment documentation for the current IP ranges.

---

Webhook Configuration

For webhook integrations, provide the target endpoint and optional authentication.

Setting	Description
Endpoint URL	The HTTPS URL that receives the event payload.
Secret Token	An optional shared secret sent in the X-Datafi-Signature header for payload verification.
Retry Policy	Number of retry attempts on delivery failure (default: 3, with exponential backoff).

Webhook payloads are delivered as JSON with the following structure:

{
  "event_type": "data_source.connection_lost",
  "priority": "critical",
  "timestamp": "2025-01-15T14:30:00Z",
  "workspace_id": "ws_abc123",
  "payload": {
    "datasource_name": "Production Snowflake",
    "error": "Connection timeout after 30s"
  }
}

---

Next Steps

• Workspace Management -- Configure workspace-level settings.
• User Management -- Manage users who receive notifications.
• AI/ML Configuration -- Set up AI event sources.