Catch the problem nobody wrote an alert for

Maple learns how each service behaves at each hour of the day. When error rate, latency, traffic or one error type moves far outside that, it opens an anomaly with the numbers behind it.

Start free trial

In motion

One service against its own week

The band is checkout's p95 at this hour over the last 7 days. Two checks in a row far above it open an anomaly. At four times the baseline it is critical.

anomalies · checkout · latency_p95 LIVE

p95 latency · last 3h baseline · same hour ±1, 7 days

healthy open · critical breaching checks 0/2 1/2 2/2

anomaly no rule

service checkout

environment production

observed 1,240 ms

baseline 310 ms

threshold 465 ms

deviation 4.0× baseline

Open investigation Link issue

checked every 5 min · opens after 2 breaches resolves after 3 healthy checks

What it does

What Maple watches

Error rate: The share of failed requests per service and environment, against the same hours last week. A service needs 50 requests in the hour before it is judged.
p95 latency: Slowdowns far outside the band and at least 50 ms slower. A nightly batch that is always slow is part of the baseline.
Traffic loss: A busy service that drops to almost nothing. A slow Sunday does not count. Losing 95% of normal traffic does.
Error spikes: One error type firing far more often than usual in 30 minutes. Spikes on the same service are grouped and linked to their issues.
Error logs: A jump in error-level logs per service, for failures that never show up as a failed span.
Investigated for you: Open an investigation from any anomaly, or turn on AI triage and an agent looks into each new one and attaches what it found.

Catch the problem nobody wrote an alert for

One service against its own week

What Maple watches

Related features

Alerting

Error Tracking

Service Catalog & Map

API Performance

Point OTLP at Maple.