mankz

Sure:

https://sting.co/ https://www.abi.se/ and lots more listed at https://www.sisp.se/medlemmar

* { font-size: 5000% !important; color:#000 !important; }

Grouping of headers + rows supported. https://bryntum.com/examples/grid/grouping/

Pivot on the way, ETA Q1/Q2 2022

Would love to hear any additional features you feel should be present in a full fledged grid package.

Not per year! The EUL license is USD 680/developer and is *perpetual* + support & upgrades are optional.

+100 for Webstorm support yes! :)

We also allow you to attach any custom data to the error report. But this doesn't necessarily help you put the web application into the state where it crashes. Demo of custom data:

https://app.therootcause.io/sandbox/addingcustomdata/

Race condition bugs are very tricky to reproduce indeed. While there will never be a guarantee our Live Replay will reproduce your issue - it should be possible since we replay all events in the exact sequence they were recorded. Our replay studio also has a 'Preserve timing' setting which uses the same delay between the events.

You could, but the point is that the stacktrace is useless in most apps (unless you have stateless minimalist website). As soon as you make a web app and you have state - stacktrace doesn't help reproduce the bug.

Sounds you had a very bad experience with Ext JS, but we hope you'll give RootCause a go anyway :)

You sum it up well. If you just get static text (call stack etc) from your error logger tool, it's of almost no use as it doesn't reveal the state of the app. With modern tools that have replay capability, this changes and the debugging process is so much nicer. :)

Taken already

Very valid points, great feedback and we completely agree, here's how we address this:

1. We recommend all our users to use the opt-in prompt before an error is logged. Demo: https://app.therootcause.io/sandbox/confirmation/

2. We can also show a special icon in bottom right corner when video is recorded. Demo: https://app.therootcause.io/sandbox/videorecording/

And, it's not just about production sites - another use case is using this internally as a tool between QA <-> Developers to speed up communication when new errors are found.

RootCause offers all js-error logging features from Sentry/Sessionstack plus our Live Replay feature.

We'll have a CDN up shortly, good point! You can also host the JS script yourself, or use the on-premises version (Docker image)

The RootCause API has multiple ways to scrub PII details from the session before posting it. And we also offer an on-premises version (Docker image) so that the data never leaves your own servers.

Curious - why does it matter to you if the UI is built using Ext, Vue or React?

Site back up :)

LogRocket is very neat looking but only does replay for Redux apps (as far as I know).

We record all events for any web app so you can replay session and fire the exact same mouse+keyboard+ajax events to reproduce the issue. Very similar tools but we wanted to make something generic targeting every web app

Issue with GoDaddy load balancing :( We're on the phone with them now

Not really no. How do you value your own time?

Here's what my Firebug Net tab tells me:

GET ext-all.js 304 OK cdn.sencha.io 442.4 KB 253ms

GET gnt-all-debug.js 304 Not Modified bryntum.com 282.4 KB 251ms

With a clean Chrome, purged cache: I get "38 requests ❘ 829.55KB transferred ❘ 1.52s (onload: 1.07s, DOMContentLoaded: 1.07s)"

And this is still without making any effort to custom build Ext JS. We're using ext-all.js for simplicity, and to make use of Sencha's CDN which should speed up world wide access compared to us hosting a custom file.

Hope this settles it :)

Ext Gantt is actually only 287kb, and <100 gzipped. It does depend on Ext JS but only a few UI classes (TreePanel, Form, TextField etc), so using a custom built Ext JS should bring this down to a very reasonable size (nowhere near 2MB for sure). :)

/Mats (Bryntum founder)

Might be biased as I wrote one of those, but feel free to email me with questions or suggestions for improvements :)

/mats(at)ext-scheduler.com