Server errors
Exceptions on your servers show in the same Errors list as the browser’s, grouped by the same rule. You send them over OpenTelemetry (OTLP), with your traces and logs. Nothing of Ottertrail’s own runs on your servers. To set up sending, see Send telemetry.
Exceptions on spans and in log records
Section titled “Exceptions on spans and in log records”OpenTelemetry records an exception in one of two ways. Ottertrail turns both into an error:
- On a span: a span event named
exception, withexception.typeorexception.message. Ottertrail takes the first 10 such events of a span. - In a log record: a log record with
exception.typeorexception.messageamong its attributes.
Only records that Ottertrail stores make errors. A span or log record that is refused makes none.
What each error holds
Section titled “What each error holds”| Field | Comes from |
|---|---|
| Type | exception.type. Error when only a message is given. Up to 200 characters. |
| Message | exception.message. Up to 2,000 characters. |
| Stack | exception.stacktrace. Up to 16,000 characters. |
| Environment, release, service | The resource’s deployment.environment.name, service.version, and service.name. Without an environment, production. |
| Route | The span’s http.route. For a log record, its own http.route, if it has one. |
| User | The record’s user.id, or the older enduser.id (see below). |
| Trace and span | The span’s trace ID and span ID. A log record without a trace has none. |
Ottertrail cuts longer values to these limits, the same limits as the browser’s errors.
A server has no visitor, browser, operating system, or location. So a server’s error counts towards a group’s users, but never its visitors.
Caught or not
Section titled “Caught or not”The error page marks an error Caught when it was handled:
- An exception on a span counts as caught, unless the span’s status is
ERROR. - An exception in a log record counts as caught when its severity is below error (
severity_number1 to 16). From error up (17 to 24), or without a severity, it counts as not caught.
An exception on a span takes the time of its span event when that falls within the span, and otherwise the span’s start. One in a log record takes the record’s time. Ottertrail trusts your servers’ clocks and does not correct them.
Retries
Section titled “Retries”A retried request makes the same errors, and Ottertrail keeps each one once. Ottertrail answers only after it has stored both the telemetry and the errors. If it cannot, it answers 503, and your exporter sends the request again.
Users from user.id
Section titled “Users from user.id”When a span or log record has a user.id attribute (or enduser.id), the error belongs to that user, and shows on the user’s page. The ID follows the same rules as the browser’s: 1 to 200 characters, without control characters. Another value is left out.
Use the same IDs that your pages give the tracker, so that a user’s browser errors and server errors are together. See Name signed-in users.
A server’s user ID is not signed. It comes with the project’s secret key, which only your servers have.
On the error’s page
Section titled “On the error’s page”A group of server exceptions shows:
- A Server card with the latest occurrence’s service, trace ID, and span ID.
- Service and Trace columns in the latest occurrences.
- Routes and services under Where it happens, in place of pages, browsers, and operating systems.
Each trace ID is a link that opens the trace on the span where the exception happened. See Traces.
Errors are kept as long as the project’s events. Traces are kept 30 days by default. So an old error can outlive its trace, and then the trace’s page says the trace is no longer kept.
A group can hold both browser and server occurrences, when the same type, message, and file appear in both. Then the columns of the latest occurrences and the tables under Where it happens cover both.
Grouping
Section titled “Grouping”Server exceptions are grouped by the same fingerprint as browser errors: the type, the message, and the top frame’s file. Ottertrail reads stacks of Node.js, Python, Ruby, Go, Java and other JVM languages, and .NET. See How errors are grouped.
Stacks are not mapped
Section titled “Stacks are not mapped”A server’s stack is shown as your server sent it. Source maps are for browser code, and Ottertrail never applies them to a server’s stack.
Alerts
Section titled “Alerts”Alert rules for new, regressed, and spiking errors watch server errors too. See Alert rules.