Alerts

Alert rules for error spikes, rate thresholds, and dead services. AI-powered creation.


Alert Conditions

  • Error Spike — Fires when error count exceeds a threshold within a time window.
  • Error Rate — Fires when the error percentage exceeds a threshold.
  • Log Contains — Fires when logs matching a pattern exceed a threshold.
  • New Error — Fires when a new error type is detected.
  • 5xx Spike — Fires when server errors exceed a threshold.
  • No Logs — Fires when no logs are received for a period (dead service detection).

Creating an Alert

Click "Create Alert" and configure a name, condition, threshold, time window, optional filters (service, pattern, log level), notification channels (email and/or webhook URLs), and cooldown period.

AI-Powered Alert Creation

If AI features are enabled, type a description like "Alert me if checkout errors spike" in the input at the top of the Alerts page and click Create. Lognitor AI will generate an alert configuration, show you a preview, and let you activate it directly or edit manually.

AI-Suggested Alerts

Click "Suggest" to have AI analyze your recent data and recommend alert rules based on your application's patterns.

Managing Alerts

  • Enable/Disable — Toggle alerts on or off without deleting them.
  • Snooze — Temporarily silence an alert.
  • Edit — Modify any alert's configuration.
  • Delete — Remove an alert.
  • Preview — Before saving, preview whether an alert would have fired against your historical data.

Flapping Detection

If an alert fires too frequently, Lognitor automatically snoozes it and sends a notification that the alert is "flapping." This prevents notification fatigue.