Increase the number of frames in axios stack traces?

[Tofandel]

By default the fingerprinting uses the stack trace, but it only uses the last 5 function calls, is it possible to increase this somehow? (7 would be much better)

Because with axios a stack trace of 5 functions is not enough to go back to the line that caused the issue.. And so I'm getting tons of unrelated errors merged together

Example
Event 1

Event 2

And the stack trace in the sentry UI is completely useless, only the breadcrumbs gives me some indication of the issue :(

Am I getting this right that the stack trace is limited to 5 or is it actually an issue with the fact that the error occurs asynchronously from what caused it?

What kind of setting change can I do to improve this?

[kamilogorek]

Am I getting this right that the stack trace is limited to 5 or is it actually an issue with the fact that the error occurs asynchronously from what caused it?

It is actually an issue with axios. We don't limit stacktraces in any way.

https://github.com/axios/axios/blob/master/lib/core/createError.js
https://github.com/axios/axios/blob/master/lib/core/enhanceError.js

The stacktrace is created not on the call-site, but rather during new Error call, in createError.js, and it's not overridden in enhanceError afterwards.

You can play around with extracting the data out of it yourself, using isAxiosError flag they provide.

Sentry.init({
  beforeSend(event, hint) {
    if (hint.originalException?.isAxiosError) {
      // do some extraction magic from request, response, code or anything else
    }
    return event;
  }
})

or you can use https://docs.sentry.io/platforms/node/configuration/integrations/pluggable-integrations/#extraerrordata integration that will do that for you.

Cheers!

[mdefeche]

Leaving a comment for those who might have the same issue.

The issue came from an old version of Axios with this issue axios/axios#4718. Upgrading to the latest issue fixed it.