Alerts

Never find out from your users again.

Alerts continuously watch the events flowing through your application.

When an event matches the conditions you define, OneMinute Logs immediately notifies you through your preferred channels.

Instead of checking dashboards every few minutes or discovering problems after customers report them, you'll know the moment something important happens. Every alert is translated into plain English before you save it, so you always know exactly what will trigger a notification.

Available on Starter and higher

Alerts are not included on the Free plan. Upgrade to Starter or a higher plan to create alerts and receive webhook notifications. View pricing.

Why alerts matter

Production problems rarely announce themselves.

A payment gateway starts failing.

An external API begins timing out.

A background job silently stops processing.

A database query suddenly becomes slow.

Without alerts, these issues often go unnoticed until users complain or revenue is already affected.

Alerts help you respond immediately instead of investigating hours later.

How alerts work

Creating an alert feels like writing an IF statement in plain English.

1Name the alertGive it a name you will recognize later, like Payment failures or Critical billing errors.

2Build the rule in plain EnglishChoose fields like App Name, Type, Importance, Service, or Message. No SQL, regex, or query language.

3Set a thresholdTrigger after a number of matching logs within a time window, like 5 matching logs within 5 minutes.

4Add a webhookSend the notification to your app, Slack bridge, Discord bridge, email service, PagerDuty, or any system that accepts webhooks.

5Choose a cooldownPrevent repeated notifications while the same issue is still happening.

From then on, OneMinute Logs continuously evaluates incoming events and sends a notification whenever your conditions match.

What the alert builder creates

You do not write rules by hand. You choose fields, operators, values, and a threshold. OneMinute Logs turns that into a readable summary before you save it.

Required app filter

App Name equals my-app

Every alert starts by choosing the app it should watch.

Event conditions

Type equals error and Importance equals critical

Add only the fields that matter for this alert.

Trigger threshold

At least 5 times within 5 minutes

Avoid one-off noise and catch repeated production issues.

Delivery

POST to your webhook URL

Receive the alert wherever your team already works.

Example summary

This alert will trigger when App Name is my-app and Type is error and Importance is critical at least 5 times within 5 minutes.

What can you monitor?

Create alerts using fields like Message, Type, Importance, Service, Subsystem, Operation, Environment, and App Name. Alerts can trigger after an event occurs multiple times within a time window, helping reduce false alarms.

Examples include:

Payment failures
HTTP 500 errors
Authentication failures
Queue processing errors
Background job failures
Slow database queries
Third-party API outages
High importance events
Custom business events

If you can send it as an event, you can create an alert for it.

Designed to reduce noise

The goal isn't to notify you about everything.

The goal is to notify you only when something deserves your attention.

Use filters, thresholds, and cooldown periods to reduce notification fatigue while making sure important incidents are never missed.

What's next?

Now that you understand how alerts work, it's time to create your first alert and receive your first notification.

NextCreate Your First Alert