"I love RootCause | Monitor & Reproduce Javascript Errors - RootCause"

2022-06-20 17:43:27

Toggle navigation PRICINGRESOURCES FEATURE TOURDOCUMENTATIONDEMO SANDBOXFORUMBLOGTERMS OF SERVICEOUR PRIVACY POLICYCONTACTBLOGSIGN INFREE TRIAL section#themo_page_header_1{background-color:#0088d1; background-image:url('https://therootcause.io/wp-content/uploads/2015/11/a_is_undefined-2.png'); background-attachment:scroll; background-repeat:no-repeat;}section#themo_page_header_1{padding-top:100px; padding-bottom:100px} Find JavaScript bugs fasterRecord videos of user sessions to easily reproduce JavaScript errors without having to ask end user for details. Try a demo in our online sandbox. Sign UpTry our demos section#themo_tour_1_0{}section#themo_tour_1_0{padding-top:70px; padding-bottom:70px}THE COMPLETE ERROR MONITORING SOLUTION FOR MODERN WEB APPSRootCause provides you with a comprehensive set of tools to monitor and reproduce errors in web sites / applications. Using the built-in recorder feature you’ll know exactly what the user did. After an error has been logged, head over to the web based Replay Studio where you can replay the session to reproduce the error with one click. This means you don’t have to read call stacks or parse through huge logs to be able to reproduce bugs. Using the Feedback button, you can also collect reports about visual / usability / rendering errors from your users. VIEW FEATURESsection#themo_service_block_1{padding-top:110px; padding-bottom:50px} How it works: var logger = new RC.Logger({ applicationId : 'yourAppId', recordUserActions : true, maxNbrOfReportedErrors : 1, logResourceLoadFailures : true, logAjaxRequests : true, captureScreenshot : true}); ADD OUR SCRIPT TO YOUR WEB PAGESInclude a small script on your page which installs a “catch-all” exception handler. The script also records all user interaction, ajax requests, console logs and other interesting data.GET NOTIFIEDWhen an unhandled exception happens, an error report is created and sent to the server using a secure HTTPS channel. We’ll notify you via email or Slack, don’t worry. You decide if and when you are notified, with intervals ranging from once per minute up to once per week. Docs hereREPLAY THE USER SESSIONThere is no faster way to debug an error, than to have it reproduced live in your browser. With our session replay feature, you simply click play and have a cup of coffee while the exception is being reproduced in your browser. No need to ask the end-user what he or she did. We also support video replay of the session. Try a demo!DEBUG WITH A BREAKPOINTAfter replaying a session the error will be triggered and you will have an active breakpoint, just as if you manually performed all the steps yourself. Debugging doesn’t get easier than when you have error reproduced live in your browser.SAVE TIME AND MONEYYou will save tons of time since you no longer have to manually communicate with end users or QA to learn how they triggered that bug. You can now reproduce a bug in minutes and fixing bugs will actually be fun (trust us).section#themo_call_to_action_1{background-color:#0088d1;}section#themo_call_to_action_1{padding-top:55px; padding-bottom:55px}Ready to try a new debugging experience?Get started for free Super cool talk and demo at @helsinkijs by @the_rootcause. These guys will save you hours of debugging!!— Gonçalo Pestana (@gpestana) March 9, 2017Mats' #senchacon presentation on @bryntum error logging is impressive as hell and well timed for us.— Disnebraska (@hobaird) November 9, 2016 ResourcesDocumentationForumsRequest a featureTerms of serviceDemo SandboxContact usCreditsView other Bryntum products Contact UsEmail Us+46 736606088Mäster Samuelsgatan 36, Stockholm, Sweden Connect With Us Recent PostsExporting RootCause Errors to JiraApril 1, 2020GDPR – Terms of Service UpdatedMay 23, 2018Announcing the new GitHub integrationMarch 28, 2018Use Case: Recording Video Of Failing Test Cases With RootCauseFebruary 26, 2018  © 2022 Bryntum .cc-window.cc-banner{ padding: 0.4em 1.8em; z-index: 1000000; font-family: inherit; font-size: inherit; } .cc-btn.cc-dismiss { font-weight:normal; } a.cc-btn.cc-dismiss { padding: .2em .4em; } a.cc-btn.cc-dismiss:hover { background-color:#aaa; }