You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello @akovalov 👋. At this moment our SDK doesn't collect backtraces for errors collected with logger.error(). Although you could implement it by your own with leveraging Thread. callStackSymbols() and sending it as log attribute, this may not work reliably if debug symbols are stripped out in release build.
Today, we only symbolicate crashes if dSYMs are uploaded to Datadog. Symbolication isn't yet supported for other kind of errors (log errors, span errors nor manually collected RUM errors), hence we don't collect stack trace as part of them.
Is it possible to have a stack trace for the error type log in the iOS SDK?
For example, if the error was logged as
How to get the stack trace that led to this error? Can SDK automatically attach it or need manually pass somehow?
Thanks
The text was updated successfully, but these errors were encountered: