Datadog support #49

Activity

1. alexfanatics commented on Mar 5, 2024

   

   alexfanatics

   on Mar 5, 2024

   Last edited by alexfanatics

   More actions

   We looked into this for a bit too. I think the main issue with Datadog compatibility is symbolication of exception stack traces.

   Symbolication isn't yet supported for other kind of errors (log errors, span errors nor manually collected RUM errors)

   DataDog/dd-sdk-ios#1572 (comment)

   Crashlytics + Bugsnag have an easy API to log an Exception along with the stacktrace which will be symbolicated on the web app, but it seems that Datadog does not support this.

   // firebase
   val exceptionClassName = throwable::class.qualifiedName
   val exModel = FIRExceptionModel.exceptionModelWithName(exceptionClassName, throwable.message)!!
   exModel.setStackTrace(throwable.getFilteredStackTraceAddresses().map { FIRStackFrame.stackFrameWithAddress(it.convert()) })
   FIRCrashlytics.crashlytics().recordExceptionModel(exModel)
   
   // bugsnag
   val exception = throwable.asNSException()
   val causes = throwable.causes.map { it.asNSException() }
   // Notify will persist unhandled events, so we can safely terminate afterwards.
   // https://github.com/bugsnag/bugsnag-cocoa/blob/6bcd46f5f8dc06ac26537875d501f02b27d219a9/Bugsnag/Client/BugsnagClient.m#L744
   Bugsnag.notify(exception) { event ->
       if (event == null) return@notify true
   
       if (handled) {
           event.severity = BSGSeverity.BSGSeverityWarning
       } else {
           event.unhandled = true
           event.severity = BSGSeverity.BSGSeverityError
       }
   
       if (causes.isNotEmpty()) {
           event.errors += causes.map { it.asBugsnagError() }
       }
   
       true
   }
2. touchlab

   locked and limited conversation to collaborators on Jul 7, 2026
3. wellingtoncosta

   converted this issue into a discussion #89 on Jul 7, 2026