Skip to content
LogZuno

Real-time alerts on any event, number or schedule

An alert is only useful if it arrives where you already are, about something you'd act on. LogZuno alerts on single events, on numbers crossing a line, and on a schedule, and sends them to email, Slack, Discord, Telegram, webhooks or browser push.
The LogZuno alerts page: event, threshold and report alerts with their destinations
  • 4 kinds of alert

    Events, thresholds, scheduled reports and AI visibility.

  • 6 kinds of destination

    Email, Slack, Discord, Telegram, webhooks and browser push.

  • Test sends

    Send a test to any destination before you rely on it.

  • 90-day delivery log

    Every delivery and every failure, kept.

Four kinds of alert

  • Instant event alerts

    Fire the moment an event matches your filters on the event, user or group, with a message template. A per-minute limit sends a summary instead of a flood.

  • Thresholds

    Watch any number chart and fire when it goes above or below a value, or changes by a percentage. Fires once, then re-arms.

  • Scheduled reports

    A chart's numbers daily, weekly or monthly, in the project's timezone.

  • AI visibility alerts

    AI fetches for people dropping or spiking, crawler requests, errors served to AI, impostors and visits from AI.

Where alerts go

  • Email

    To organisation members.

  • Slack and Discord

    To a channel, through an incoming webhook.

  • Telegram

    To any chat, linked with a one-time code from the LogZuno bot.

  • Webhooks

    Signed JSON to any public HTTPS address, so you can verify it came from LogZuno.

  • Browser push

    To each team member's browser, opted in per browser.

Illustration: LogZuno alert destinations: email, Slack, Discord, Telegram, a signed webhook and browser push, each with a test send.

Quiet when it should be

  • Snooze and pause

    Snooze an alert or turn it off without deleting it.

  • Test sends

    Send a test to any destination before you rely on it.

  • Delivery log

    Every delivery and failure kept for 90 days.

  • Weekly report

    A Monday summary per project, by email or browser push, chosen by each member.

Illustration: a LogZuno event alert for failed payments over 100, with its destinations, test, snooze and pause controls, and a delivery log that includes a failed webhook.

Questions

Is there a limit on the number of alerts?

No. Every plan can create as many alerts and destinations as it needs.

How do I know a webhook came from LogZuno?

Each webhook is signed with a secret only you and LogZuno know. Check the signature header before you trust the payload.

What are real-time alerts?

Notifications sent the moment something happens, instead of in a report later. In LogZuno, an instant alert fires when a single event matches your filters, such as a failed payment over 100, and posts to the destinations you choose.

How quickly do alerts arrive?

Instant alerts are checked as events are ingested, so they reach Slack, email or your browser within seconds of the event being sent.

How do threshold alerts work?

Pick any number chart and a condition: above a value, below a value, or a change by a percentage. The alert fires once when the condition is met, then re-arms when it clears, so you're not told the same thing every minute.

How do I stop an alert from flooding a channel?

Instant alerts have a per-minute limit; past it, LogZuno sends one summary instead of many messages. You can also snooze an alert or turn it off without deleting it.

Can I test an alert before relying on it?

Yes. Send a test to any destination from its settings, and check the delivery log, which keeps every delivery and failure for 90 days.

Send your first event today.

7 days free on any plan, up to 500 events. Then from $17 a month. Cancel during the trial and you pay nothing.