142 errors, one issue

Maple groups the same error into one issue and links every occurrence to the span that threw it.

Start free trial View on GitHub

The surface

Errors grouped into issues

Each issue shows its type, affected services, count and when it was last seen.

Errors grouped by type with counts, affected services and last-seen times
/errors ConnectionTimeout · payment-svc
groups.by
exception.type + message
normalizes
ids · hashes · hosts · emails
per.issue
first · last · count · services
joins.on
trace_id · span_id
severity
manual > ai > detector
groups
every minute

More screens

Error Tracking, screen by screen

/errors/issues/:id One issue, every occurrence
The ConnectionTimeout issue open with its stack trace, trend and affected traces
/traces The trace behind it
A failing checkout opened from the issue, showing the span that threw

What it does

From issue to fix

fingerprint
Grouping
Errors with the same type, message and stack are one issue. Ids, hosts and emails are ignored when matching.
exception.stacktrace
The span that threw it
Every issue opens the trace it came from, with the query and status code at the time.
first seen
New or back again
See when an issue first and last appeared. A resolved issue that comes back reopens.
claim
Owners and notes
Claim an issue, set severity and leave notes, so the next person on call knows what you tried.
set severity
Triaged automatically
New errors are grouped every minute and AI suggests a severity. Your choice always overrides it.

Keep going

Related features

01

Distributed Tracing

Follow every request across services

→ 02

Alerting

Alert on any signal, routed where you work

→ 03

AI & MCP Integration

Let Claude or Cursor query your traces, logs and metrics

→ 04

E-Commerce Observability

Trace a failed checkout by its order id

→

Point OTLP at Maple.

One endpoint, one key. Traces, logs, metrics and sessions, linked from the first request.

Start free trial View on GitHub