tide — Clean, warm components for React apps

What you get

See the problem, the cause and the owner on one screen

Five things teams notice in their first week.

1. Cart
  12,480
  100%
2. Shipping
  9,214
  73.8%
3. Payment
  5,106
  55.4% (largest drop-off)
4. Paid
  4,683
  91.7%
Catch the slow step before customers do
Every deploy is traced end to end. Brightline found a 1.8 s checkout call in its first hour.
99.98%
99.98% uptime, in public
A status page your customers can read, updated by the same checks your team sees.
- POST /checkout1840 ms
- GET /search912 ms
- GET /orders/:id377 ms
Know which endpoint costs most
Requests ranked by total time, so the fix with the biggest payoff is always on top.
npm i @brightline/trace
Install in one line
One package, no agents to run. Traces start with the next request.
p95 over 800 ms on /searchv4.12.1
Error rate back under 0.1%Resolved
Alerts that say what broke
Each alert names the release, the endpoint and the owner, so nobody guesses at 3 a.m.

What you get

Five things teams notice in their first week.

1. Cart
  12,480
  100%
2. Shipping
  9,214
  73.8%
3. Payment
  5,106
  55.4% (largest drop-off)
4. Paid
  4,683
  91.7%
Catch the slow step before customers do
Every deploy is traced end to end. Brightline found a 1.8 s checkout call in its first hour.
99.98%
99.98% uptime, in public
A status page your customers can read, updated by the same checks your team sees.
- POST /checkout1840 ms
- GET /search912 ms
- GET /orders/:id377 ms
Know which endpoint costs most
Requests ranked by total time, so the fix with the biggest payoff is always on top.
npm i @brightline/trace
Install in one line
One package, no agents to run. Traces start with the next request.
p95 over 800 ms on /searchv4.12.1
Error rate back under 0.1%Resolved
Alerts that say what broke
Each alert names the release, the endpoint and the owner, so nobody guesses at 3 a.m.