Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

feat: add Sentry support for Ktor Client (error handling, breadcrumbs) #25

Open
buenaflor opened this issue Aug 5, 2022 · 4 comments
Open

feat: add Sentry support for Ktor Client (error handling, breadcrumbs) #25

buenaflor opened this issue Aug 5, 2022 · 4 comments
Labels
Platform: KMP Type: Feature Request

Comments

@buenaflor
Copy link
Contributor

buenaflor commented Aug 5, 2022 •
edited

We could add support for Ktor HttpClient to intercept requests and add error handling similar to the Java OkHttp / Apache support.
@buenaflor buenaflor changed the title feat: Add Sentry support for Ktor Client feat: add Sentry support for Ktor Client Aug 5, 2022
@Legion2
Copy link

Legion2 commented Apr 26, 2023

Have a look at OpenTelemetry Tracing for Ktor, to get an idea of how Sentry can instrument ktor.

@buenaflor
Copy link
Contributor Author

@Legion2 thx for the suggestion! It might take some time until we get to a ktor client support as it depends on #83

@markushi
Copy link
Member

Related issue: getsentry/sentry-java#2684

@buenaflor buenaflor changed the title feat: add Sentry support for Ktor Client feat: add Sentry support for Ktor Client (error handling, breadcrumbs) Jul 18, 2023
@buenaflor buenaflor mentioned this issue Jul 18, 2023
Open
@buenaflor
Copy link
Contributor Author

As we will focus on error handling and breadcrumbs for ktor client in this issue, we have moved the discussion for performance monitoring to #107

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Platform: KMP Type: Feature Request
Projects
Mobile & Cross Platform SDK
Status: Backlog
Milestone
No milestone
Development

No branches or pull requests
4 participants
@markushi @kahest @Legion2 @buenaflor