Know What User Did Before the ERROR Happened

And Fix Prod Bugs Really Fast

Sign up

Bug Fixing Stages

Bug! Gather info Report Reproduce Analyse Fix Deploy
The old way
Customer reports a problemCustomer support talks to customerCustomer support reports an issueDeveloper recreates environment and reproduces the problemDeveloper analyses the issueDeveloper fixes the issueDevOps deploys a fix to production
The Kuoll way
Kuoll script detects a problem Kuoll script captures bug report automaticallyKuoll script captures high-fidelity bug reportKuoll replays captured report in debug modeDeveloper analyses the issue with easeDeveloper fixes the issue with confidenceDevOps deploys sure fix to production
Biz Value
Finds bugs before your customers doAutomated capturing saves 68% customer support timeHigh-fidelity capturingHigh-fidelity replaySure fix, no refix ping-pong, saves 40% timeMuch easier, spends 60% less timeBugs fixed, HQ software is direct to market

Spot and quickly fix critical prod issues with slick client-side monitoring

OK, how it works

A developer copies Kuoll monitoring code snippet into pages of web application.

This code is monitoring js and server problems and recording user sessions. User sessions are stored on the client-side in the user web browser internal database (called IndexedDB).

When a problem detected,` Kuoll dumps the user session to the server. In case of a newly discovered problem, we send developer a link to recorded user session to Slack.

An engineer gets notification with a link where he can see the recorded user session. Each user session shows the developer

  • user events,
  • replayable DOM-mutations,
  • network requests (with a complete headers and content),
  • JavaScript execution flow, including Promise call, setTimeout, setInterval.

All events are connected to the cause-effect chains. A developer is able to see and analyse the bug on the record, without even reproducing it, and fix the issue xtremely fast.