LuminaLog
Waitlist
Notifications

Alerts & Notifications

Get notified instantly when critical errors occur. Set up custom alert rules and route notifications to Slack, Discord, PagerDuty, or email.

How Alerts Work

LuminaLog monitors your log stream and uptime monitors in real-time and triggers alerts based on precise criteria. Notifications are dispatched via our global edge network within seconds.

1
Define Rule

Set granular conditions for error types, thresholds, and severities.

2
Match Logs

Our ingestion gateway monitors logs in real-time against your active rules.

3
Dispatch Alert

Notifications are sent to your configured integration channels instantly.

Integration Channels

LuminaLog supports a wide spectrum of delivery vectors. Route different severities to different platforms for optimal on-call balance.

Slack

Webhook URL required

Rich formatting, error stack traces, and direct action buttons for incident response.

Discord

Webhook URL required

Embedded messages with full metadata support and automated role tagging.

PagerDuty

Integration key required

Create incidents with automatic escalation policies and on-call routing.

Email

Zero configuration needed

Detailed error digests sent directly to team members with deep links to reports.

Alert Rule Components

ComponentDescriptionExample
Rule NameInternal identifier for the alertCheckout Failures
Error TypeSpecific Exception to isolateOAuthError
ThresholdX events within Y minutes10 per 60 mins
ChannelsRecipient platformsSlack, PagerDuty
SummariesPeriodic roll-up notificationsHourly Digest

Configuration Examples

Critical Exceptions (Immediate)

{
  "rule_name": "High Priority Error Tracking",
  "error_type": "PaymentError",
  "severity": "error",
  "channels": ["slack", "pagerduty", "email"]
}

Trigger high-priority alerts with full context on every occurrence.

Frequency Spikes (Threshold)

{
  "rule_name": "API Rate Limit Spike",
  "count_threshold": 50,
  "time_window_minutes": 15,
  "channels": ["slack"]
}

Reduce noise by alerting only when error density exceeds safety limits.

Monitoring Resolution

{
  "rule_name": "Database Health Monitor",
  "resolved_notification": true,
  "resolved_hours": 1,
  "channels": ["slack", "email"]
}

Automatically notify the team when an error stream has stabilized.

Alert Intelligence

LuminaLog uses advanced fingerprinting to prevent alert fatigue. Identical errors are grouped naturally without manual configuration.

Smart Deduplication

Errors are grouped by type + message hash, keeping your feed clean.

Temporal Tracking

FirstSeen and LastSeen timestamps are updated for every unique trace.

Quota Guard

Auto-alerts when you reach 80% or 100% of your log storage tier.

Real-time Dispatch

Alerts move through our SNS/SQS pipeline with sub-second latency.

Best Practices

Tiered Notification Routing

Critical Errors → PagerDuty; Warnings → Slack; Info → Webhooks.

Descriptive Rule Naming

Use 'User Auth Critical Latency' instead of 'Auth Alert'.

Threshold Fine-tuning

Adjust windows (15m vs 60m) to match your team's incident SLA.

Webhook Rotation

Never commit integration keys; manage them via dashboard secrets.

Next Steps