Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Ability to control exception depth to avoid CPU spikes

See original GitHub issue

Do you want to request a feature or report a bug?

Feature.

What is the current behavior?

Raven client for NodeJS currently sets MAX_SERIALIZE_EXCEPTION_DEPTH = 3. For large exceptions from external APIs the exception objects may contain a large amount of data and nested keys, causing Sentry to spike NodeJS process, blocking all other actions.

What is the expected behavior?

captureException should allow control over how deep serializeException goes by default. Raven already has a kwargs parameter in which this could reasonably be passed down to serializeException, who’s 2nd parameter is the maximum depth.

Issue Analytics

State:
Created 5 years ago
Comments:7 (2 by maintainers)

Top GitHub Comments

1reaction

kamilogorekcommented, Jul 2, 2021

Closing the issue, as it seems like the original issue has been resolved. Please do not hesitate to ping me if it is still relevant, and I will happily reopen and work on it. Cheers!

0reactions

adriaanmeuriscommented, Mar 5, 2019

@kamilogorek any idea in which version this would become available?