Tickets and error groups
Read a ticket, follow its group and set its status.
This page explains the pages you reach from a notification, and how to tell dlogify an error is handled.
Read a ticket
A notification links to the ticket's page. It shows the report as it was written: summary, probable cause, suggested fix, severity, the facts (service, environment, release, first and last seen, occurrences) and the stack trace with the log lines before and after the event. Next to it, the page shows the error group as it is now, with its status actions.
Tickets never change after they are written. If the group spikes or regresses later, a new ticket is written.
Error groups
dlogify groups similar ERROR and WARN events into an error group. Each group has a status:
| Status | Meaning |
|---|---|
open | New or still happening |
resolved | You marked it fixed |
ignored | You do not want to hear about it |
regressed | It was resolved and happened again |
On an open or regressed group choose Resolve or Ignore; on a resolved or ignored group, Reopen. A resolved group that happens again becomes regressed and gets a new ticket. An ignored group keeps counting occurrences but never writes tickets. Every role can change a group's status.
Filters
The Tickets list filters by severity; the Error groups list filters by status and by severity. Both keep their filters in the address, so you can share a filtered view. To see the tickets of one error group, open the group: its page lists them. The API filters tickets by group with group_id on GET /v1/projects/{project_id}/tickets.
INFO summaries
INFO logs are not grouped one by one. dlogify counts them in time windows and writes a short summary of each window: totals, how they compare with the previous window, and what stood out. The window length depends on the plan. Summaries appear under INFO summaries and in digests.