Stack trace features?

[dandv]

Any plans for this? Nothing fancy like TrackJS's telemetry, but at least backtraces like the ones provided by Rollbar, Airbrake, or GetSentry.

[mostlyjason]

sendConsoleErrors value to true will send all the unhandled errors to the Loggly. Does this match what you're looking for?

[varshneyjayant]

@dandv Try setting

_LTracker.push({
                'logglyKey' : 'your-key',
                'sendConsoleErrors' : true
            });

You should be able to send stacktraces to Loggly.

[dandv]

Here's what I mean by a stack trace:

Judging by its description, sendConsoleErrors only seems to log unhandled errors, but there is no mention of stack traces on the client at https://www.loggly.com/docs/javascript/.

[varshneyjayant]

@dandv are you talking about catched errors? or stack traces of unhandled errors?

[dandv]

I'm looking for a client-side JS error logger for both caught and uncaught errors. Rollbar and {Track:js} seem to do the best job at the so far. See rollbar/rollbar.js#108.

[andrewmclagan]

yeah the current functionality leaves allot to be desired

[iamtchelo]

I have a question. I have a minified js file and it's impossible to get a real error, for this problem I need to generate a source map file for each javascript file. How Loggy deals with it? @varshneyjayant

[varshneyjayant]

@marcelodeveloper Loggly has source map for loggly-jslogger
https://github.com/loggly/loggly-jslogger/blob/master/src/loggly.tracker-2.1.min.map

[iamtchelo]

Sorry, I think that I didn't explain myself correctly. I have an app built using requirejs and I am generating the source map files for each one. My problem is that when I send to loggly the error exception I can't see the not-compiled version in the dashboard. Is it possible to see the non-compiled version instead of the compiled version in Loggly? Maybe there is a way to say Loggly to use the source map files before send the log exception. In that way I could see the error line and row easily and don't try to guess where the error happened. Thanks @varshneyjayant

[apackin]

We were experiencing the same issue as described by @marcelodeveloper .
We're using something similar to what is PRed above if you're interested @varshneyjayant

[fastfrwrd]

For reference, this article on Sentry's blog thoroughly covers the implementation details to get a cross-browser stack trace. It's not trivial - you need to to invasively augment methods like setTimeout and addEventListener. https://blog.sentry.io/2016/01/04/client-javascript-reporting-window-onerror.html

[varshneyjayant]

@mostlyjason @Shwetajain148

[mostlyjason]

Thanks for the link! We will review this next time we do an update of the JavaScript library, but there are a few other projects ahead of this one in the queue.

[Cphilo]

Any update?