Errors
See the error before the email.
Errors from your pages, servers and apps, grouped into issues, scrubbed before they are stored, and linked to the trace they happened in.

Issues, not noise.
The same error a thousand times is one issue. LogSure groups by type, by the message with its numbers and IDs taken out, and by the top frames of your own code, with build hashes ignored.
- Events, users and a sparkline per issue
- The first frame of your code, the release and the environment
- Resolve, ignore, or add a note for the team
- A resolved issue that comes back opens again

It catches what you didn't.
Send the errors you catch with one call. Turn on, per app, what the tracker may catch by itself; everything is off until you do.
- Uncaught errors and rejected promises
console.errorcalls, which still log- Requests that fail or answer 5xx, 4xx if you choose: the method, the address, the status and the time, never bodies or headers
- Scripts, style sheets and images that do not load

From the error to its trace.
An exception on an OpenTelemetry span, or a log at ERROR, becomes an occurrence too. Open it, and View trace shows the request it broke, span by span.
Learn more about tracing
Safe to keep. Loud when it matters.
How it works.
Name the release
The tracker you already have, with the release and environment on the tag.
<script defer data-app="example-shop"
data-release="2.4.1"
data-environment="production"
src="/_care/script.js"></script>
Send what you catch
Any error, with properties. Turn on automatic capture in the app's settings.
try {
checkout();
} catch (err) {
logsure.error(err, { step: 'checkout' });
}
Report from servers
Back-ends and native apps post with the app's server key.
curl -X POST $LOGSURE_URL/_care/error \
-H "authorization: Bearer $LOGSURE_KEY" \
-d '{"message":"Card declined",
"release":"api-1.18.0"}'