Notifications

Stay informed about critical events with EdLog's multi-channel notification system. Send alerts via email, Slack, Discord, SMS, and custom webhooks when tiles change state or specific conditions are met.

Supported Channels

Email

SMTP-based email notifications to multiple recipients

Slack

Team notifications via Slack webhooks

Discord

Discord server notifications

Pushover

Mobile push notifications

SMS

Text messages via Twilio

Webhook

Custom HTTP endpoints

Setting Up Notifications

  1. Navigate to Notifications in the sidebar
  2. Click Add Service
  3. Select your notification channel type
  4. Enter the required configuration:
    • Service name for identification
    • Channel-specific credentials
    • Optional test mode for development
  5. Click Send Test to verify configuration
  6. Save the notification service

Triggering Notifications

From Tile Rules

Add notification actions to your tile rules to alert when conditions are met:

  • State changes (OK → Error)
  • Threshold breaches
  • Specific event patterns

Manual Alerts

Send test notifications or manual alerts from the UI:

  • Test service configuration
  • Send custom messages
  • Broadcast to all channels

Via API

Trigger notifications programmatically: 

POST /api/v1/notifications/{service_id}/send
{
  "subject": "Alert Title",
  "body": "Alert message content"
}

Notification Templates

Use variables in your notification messages to include event data:

Example template:

🚨 {tile.name} is now {tile.state}

Project: {project.name}
Event: {event.name}
Message: {event.attributes.message}
Time: {event.timestamp}

View dashboard: {dashboard_url}

Available variables:

  • {tile.*} - Tile properties
  • {event.*} - Event fields
  • {project.*} - Project details
  • {attributes.*} - Event attributes

Managing Notifications

  • Enable/Disable: Toggle services without deleting configuration
  • Test Mode: Send notifications to logs instead of real channels
  • Rate Limiting: Prevent notification flooding
  • Quiet Hours: Suppress non-critical alerts during off hours
  • Escalation: Route to different channels based on severity
  • History: View all sent notifications and delivery status

Best Practices

  • • Test all notification channels before relying on them
  • • Use different channels for different severity levels
  • • Include actionable information in messages
  • • Set up redundant channels for critical alerts
  • • Use rate limiting to prevent alert fatigue
  • • Document escalation procedures
  • • Regularly review and update notification rules

Next Steps