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
I am implementing a API backend in Kotlin using Ktor, a popular Kotlin web framework that uses coroutines for requests. I am testing using Bugsnag since I already use that for Android. However, there seems no support for Coroutines, which frequently switch threads. So I can't store threaded metadata properly, and probably the startSession() stuff will also cause issues when multiple coroutine calls are handled.
Describe the solution you'd like
Support a form of CoroutineContext like OpenTelemetry or Sentry does.
Describe alternatives you've considered
Additional context
Quite vital for modern Kotlin web/api apps.
The text was updated successfully, but these errors were encountered:
Thank you for reaching out and raising this product feedback.
Adding some form of CoroutineContext functionality does sound like worthwhile feature. As such I have raised this with our engineering team and we now have a backlog item aimed at adding this support. However I should note that this backlog item is still in the scoping stages, as such I have no clear ETA on the release of this functionality as of right now. Once we have more information to share we will be sure to update this thread.
Description
I am implementing a API backend in Kotlin using Ktor, a popular Kotlin web framework that uses coroutines for requests. I am testing using Bugsnag since I already use that for Android. However, there seems no support for Coroutines, which frequently switch threads. So I can't store threaded metadata properly, and probably the startSession() stuff will also cause issues when multiple coroutine calls are handled.
Describe the solution you'd like
Support a form of CoroutineContext like OpenTelemetry or Sentry does.
Describe alternatives you've considered
Additional context
Quite vital for modern Kotlin web/api apps.
The text was updated successfully, but these errors were encountered: