# Introduction

> dlogify turns your application logs into full-context tickets.

dlogify reads your application's logs so you do not have to. It groups your errors, classifies them with AI and writes a ticket with everything needed to fix each one: a summary, the probable cause, a suggested fix, the stack trace and the log lines around the failure. Urgent tickets reach you by email, Slack, Discord or webhook right away; the rest arrive in a digest.

## How a log becomes a ticket

1. Your application sends its logs to dlogify ([Send logs](https://docs.dlogify.com/send-logs.md)).
2. dlogify redacts personal data and groups similar errors into an error group ([Error groups](https://docs.dlogify.com/concepts.md#error-groups)).
3. When a group is new, spikes, comes back after being resolved, or comes back after a day without events, dlogify classifies it and writes a ticket ([Tickets](https://docs.dlogify.com/concepts.md#tickets)).
4. `critical`, `high` and `medium` tickets are delivered at once; `low` tickets and the summaries of your `INFO` logs go into a digest ([Notifications](https://docs.dlogify.com/notifications.md)).

## Start here

- [Quickstart](https://docs.dlogify.com/quickstart.md): From sign-up to your first ticket in about five minutes.
- [Send logs](https://docs.dlogify.com/send-logs.md): Node.js, Python, OpenTelemetry or plain HTTP.
- [Webhooks](https://docs.dlogify.com/webhooks.md): Receive tickets in your own systems and verify them.
- [API reference](https://docs.dlogify.com/api.md): Every endpoint of the dlogify API.

Source: https://docs.dlogify.com
