# Notifications

> When dlogify notifies you and what a ticket contains.

This page explains which events reach you, when, and through which channels.

## When dlogify notifies

dlogify writes a ticket when an error group is new, when it spikes, when a resolved group happens again (a regression), or when an open group happens again after at least 24 hours without occurrences (a recurrence). Other occurrences of a group that was already reported do not notify again.

| What | Delivered |
|---|---|
| `critical`, `high` and `medium` tickets | At once |
| `low` tickets | In the next digest |
| INFO summaries | In the next digest |

Digests are sent on the schedule you choose for each project, and only when there is something to report. See [Notification settings](https://docs.dlogify.com/notifications/settings.md).

## Channels

Each project sends to its enabled channels:

- **Email** to a member of the organization, at the member's current address. The member's email must be verified. See [Email](https://docs.dlogify.com/notifications/email.md).
- **Slack** to a channel, through an incoming webhook. See [Slack](https://docs.dlogify.com/notifications/slack.md).
- **Discord** to a channel, through a channel webhook. See [Discord](https://docs.dlogify.com/notifications/discord.md).
- **Webhook** to an `https` endpoint of yours, signed with a secret. See [Webhooks](https://docs.dlogify.com/webhooks.md).

Admins and owners add channels under **Channels** in the project, with **Add channel**. The number of channels per project, and whether webhooks are available, depend on the plan; email, Slack and Discord are available on every plan ([Plans and usage](https://docs.dlogify.com/dashboard/plans-and-usage.md)).

## What a ticket contains

- A title and a summary, the probable cause and a suggested fix.
- The severity, the category, and whether the error looks transient.
- The service, environment and release.
- When the group was first and last seen, how often it happened, and why the ticket was written: new, spike, regression or recurrence.
- The stack trace and the log lines just before and after the event.

Personal data is redacted before any of this is written to dlogify's database or sent anywhere (see [Personal data](https://docs.dlogify.com/send-logs/what-is-sent.md#personal-data)). When the daily AI budget is used up, the ticket is still written and delivered, with the same facts but without the generated title, summary, cause and fix (see [Daily AI budget](https://docs.dlogify.com/dashboard/plans-and-usage.md#daily-ai-budget)).

## Delivery

Failed deliveries are retried for about 22 hours. A channel whose deliveries keep failing is marked as failing until one succeeds again. Details in [Retries](https://docs.dlogify.com/webhooks.md#retries).

Source: https://docs.dlogify.com/notifications
