dlogify docs

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, regresses or recurs later, a new ticket is written.

Error groups

dlogify groups similar ERROR and WARN events into an error group. Each group has a status:

StatusMeaning
openNew or still happening
resolvedYou marked it fixed
ignoredYou do not want to hear about it
regressedIt 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 open or regressed group that happens again after at least 24 hours without occurrences keeps its status and gets a new ticket (a recurrence). An ignored group keeps counting occurrences but never writes tickets. Every role can change a group's status.

A group's page also shows how it behaves over time: see Group history.

Mark a ticket as a reference

When a ticket helped you solve a problem, choose Mark as reference on its page, so your team can find it when something similar happens. To see them all, set Show to References in the Tickets list. Remove reference takes the mark away.

A reference is shared with your whole organization, and every role can mark tickets or remove the mark. Marking does not change the ticket, and it does not keep it longer: a reference is deleted with the ticket when your plan's retention ends. To keep it for longer, choose Copy ticket and store the text where your team keeps its notes.

The API marks a ticket with PUT /v1/tickets/{ticket_id}/reference and removes the mark with DELETE /v1/tickets/{ticket_id}/reference. Tickets show when they were marked in reference_marked_at.

Filters

The Tickets list filters by severity and by references; 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 and by references with reference=true 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.

On this page