Errors

Errors collects the crashes and exceptions your apps send through an SDK. The same fault repeated a thousand times stays one row, with its counters: you see right away how many different problems you have, not how much noise they make.

How a group forms

Every incoming error gets a fingerprint: a fixed code computed from the error itself. Errors with the same fingerprint, in the same project, go into the same group. The fingerprint is computed like this, in order:

1. if the SDK sends its own fingerprint, that one counts;
2. otherwise the exception type plus the place in the code it starts from;
3. otherwise the message, with numbers and variable codes removed;
4. otherwise the name of the request.

Variable text in the message (an id, an amount) does not split the group. If the same message appears in several groups because it starts from different places in the code, the page points it out with "One problem, in N places".

Each group has a level (debug, info, warning, error, fatal) and a status: Unresolved, Resolved or Ignored.

Read an error

Open a row of the list. At the top you find Events received, Users, the Occurrences over time chart and the release where it first appeared (Introduced in).

Below are the Recent occurrences: select a row to see that exact case, split into tabs:

• Stack trace: the lines of code it went through;
• Details: the request, the server, the runtime and the SDK;
• User, Tags and Context: what else the SDK sent;
• Session replay: the recording of the session, if there is one (see Session replays);
• Logs of this request: the logs of the same request, if they carry the same identifier.

You can filter occurrences by Environment and Release.

Users counts the different people affected. If it says "not tracked", the SDK does not send the user id: set it before the error is captured. CloseYourIt counts people with an anonymous fingerprint; emails, IPs and usernames are not stored.

Some values (passwords, tokens, emails) show as "Hidden": they are removed before saving, on purpose.

Resolve, ignore, reopen

On the error page:

• Resolve opens Resolve and explain: write the Cause and the Fix. They are optional, but they are what you will look for if the error comes back in six months.
• Ignore sets aside a noisy error you do not care about.
• Reopen makes a resolved or ignored error active again.

To sort many errors at once, select them in the list and use Resolve, Ignore or Reopen in the bar that appears.

cyi errors resolve <id> --project acme-api
cyi errors mute <id> --project acme-api      # same as Ignore
cyi errors reopen <id> --project acme-api

You need the "Triage errors" permission.

When a resolved error comes back

If a new occurrence of a Resolved error arrives, CloseYourIt reopens it by itself: it is a regression. It remembers the release where it came back, and the Regression alert rule notifies you (see Alerts).

When you resolve, CloseYourIt notes the release in use at that moment (see Releases). An occurrence coming from a release that is certainly older comes from a client that was not updated: it does not reopen the error. If the order of the releases cannot be told, the error reopens.

An Ignored error does not reopen by itself.

Turn an error into a ticket

1. Open the error and press Promote to ticket.
2. Check the preview: project, title, the place in the code, how many times it happened and the link back to the error.
3. Press Create the ticket.

A ticket of type Bug is created, linked to the error. The original message stays whole in the description. You need the "Promote error to ticket" permission.

cyi errors promote <id> --project acme-api

Merge two groups

If two groups are the same problem, select them in the list and press Merge. On the Merge errors page choose Which group stays, then press Merge permanently. Only errors of the same project can be merged.

How long occurrences are kept

Single occurrences are kept for 30 days, then deleted. The group and the Events received total stay. To change how long, open the project, then Settings and Errors retention (days): empty means using the organization's value.