open-telemetry / open-telemetry/opentelemetry-android
Feature: ignore some errors generated from http interceptors
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 297
- Forks
- 113
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 51
Description
For now, TracingInterceptor record all errors generated by http request executed in the Android application. But it could be interesting to add a way to ignore some errors like java.io.InterruptedIOException, okhttp3.internal.http2.StreamResetException (stream was reset: CANCEL) or java.io.IOException (Canceled).
All these errors are generated when a Kotlin coroutine scope is cancelled and where we are no more interested about the http response. It sounds legit to ignore the instrumentation of this kind of error.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at TracingInterceptor and inspect how errors from Android HTTP requests are currently recorded. Determine how the listed cancellation-related exceptions should be ignored, then add coverage for those cases and verify that other HTTP errors remain instrumented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, kotlin
- Domain
- mobile, observability
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100