Skip to content

Features

Alerts that tell you what changed

Buglapse tells the team when something new happens in a project: a new issue, an error that came back, a spike, a drop in stability or a service going down. Alerts arrive by email, in Telegram or in MAX — batched so that a bad deploy does not become a hundred messages.

Get startedRead the docs

All Buglapse features

Alerts

Signal without the flood

  • The events that matter

    New issues, regressed issues, ignored issues that got worse, spikes, crash-free drops, quota usage, Autofix results and uptime incidents.

  • One message, not fifty

    Alerts are collected for a few minutes and delivered as a single digest — an email or a chat message — so a burst of new issues after a deploy arrives as one notification.

  • Downtime is not delayed

    A monitor going down or recovering skips the digest window and is sent within about a minute, taking along anything else that was waiting.

  • Email, Telegram and MAX

    Every member chooses which alerts to receive by email and in a private chat with the bot. The organization owner connects the bot to the team chat and decides which projects and alert types it gets.

How it works

How alerts reach you

  1. 1

    Something happens

    A new fingerprint appears, a resolved issue receives an event, a monitor fails several checks in a row, a quota reaches its threshold.

  2. 2

    The alert is recorded

    It is saved in the alert history of the project with a link to the issue or the monitor, and queued for every subscribed member and every connected team chat.

  3. 3

    The notification goes out

    Queued alerts are sent together as a digest — by email and to the Telegram and MAX chats. If delivery fails, it is retried several times with growing pauses.

In detail

Alert types, channels and delivery

What raises an alert

Issue alerts cover a brand-new issue, a resolved issue that returned, and an ignored issue that escalated beyond what it was ignored for. A spike alert is raised when a sudden burst of events starts being sampled. A crash-free drop alert is raised when the share of crash-free sessions in the last hour falls below the threshold. Quota alerts warn the owner when a monthly quota is nearly used and when it is exhausted. Autofix alerts say that a pull request was opened or that the agent needs an answer, and uptime alerts report a monitor going down and coming back.

Telegram and MAX

The bot is connected with a one-time code from the dashboard. A private chat works like email: in your profile you choose which alerts to receive and for which projects, and quota alerts go to the owner only. A team group chat is connected by the organization owner — in Telegram the bot is added through a link, in MAX you send a command with the code to the chat — and gets a filter for the projects and alert types it receives. A message carries what the email does: the titles of issues and monitors with links to the dashboard, and a link to the alert history when not everything fits. If the bot is removed from a chat, Buglapse unlinks that chat on its own.

Digest and deduplication

Each alert is recorded once: a noisy issue does not raise the same alert again and again, and a spike is reported once per event type and hour. Pending alerts for a recipient are collected from the oldest one and sent as one email or message. The history of alerts stays in the project, so you can see what was raised and when even if the notification was missed.

On each plan

Compare all plans
On each plan
Free Pro Team
Alert history14 days30 days90 days

FAQ

Common questions

Still have questions?

Drop us a line — we'll help with setup, plans or self-hosting.

Contact us

or email hello@buglapse.com

Which channels are supported?
Email, Telegram and MAX — in a private chat with the bot or in a team group chat. Slack, webhooks and other messengers are not available yet.
Who receives alerts?
Members of the organization, each of whom chooses in their profile which alerts to receive by email and in a private chat with the bot. A team group chat gets the alerts the owner selected for it. Quota alerts are sent personally to the owner only.
Where can I see past alerts?
On the Alerts page of the project. How long the history is kept depends on the plan — see the table above.

See also

Related features

Error tracking

Every error grouped into one issue with a readable stack trace, breadcrumbs, the steps to the error and the affected users.

Learn more: Error tracking

Ready to see what's happening in your app?

Create a project on the free plan and send your first event in a couple of minutes.

Create your projectRead the quickstart

Still have questions? Email hello@buglapse.com