palantir / palantir/conjure-java-runtime
Propagate tracing information when limiter times out
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 95
- Forks
- 96
- Avg merge
- 3h 38m
- Merged PRs (30d)
- 33
Description
What happened?
I get the warning log for when a concurrency limiter has timed out, but it doesn't have a traceId.
What did you want to happen?
It would be useful to know which incoming request to my server timed out when trying to make an outbound request.
Contributor guide
No contributing guide indexed for this repository
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 in okhttp-clients/src/main/java/com/palantir/conjure/java/okhttp/ConcurrencyLimiters.java at the timeout warning around line 276. Trace how the incoming request's tracing information is available when the limiter times out, and inspect nearby logging and limiter code. Done means the timeout warning identifies the incoming request with its traceId.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, observability
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100