From the error, then a threshold.

The request, then the time each service spent, then the function. A saved search can page Slack when the count crosses a line. Mute it when you already know. Every alert opens the search behind it.

A trace waterfall of one request through nginx, php-fpm, wordpress, mysql and smtp: 412ms, 8 spans. The failed wp_mail span is selected and shows the exception it recorded: its e1, the type PHPMailer Exception, the message SMTP connect() failed, and the start of the stack.

A span keeps the exception recorded on it. Select it and the waterfall shows the type, the message and the stack, with the same e1 as the log row that logged it. An exception still has to be logged to be hunted: Fingerprints, level:error and Compare read log rows.

The slowest step broken down by function

Customer, region or environment as a prompt. Then a count, delivered to Slack.

A saved view asking which customer to look at
Alerts with thresholds, last fired and where they notify

Same hunt. We run it.

Hosted early access is planned for Q4 2026. The same product as the free self-hosted edition, operated by us.

No spam · no sales · confirm in your inbox