Tracing API Operations
- Dominant language
- Java
- Stars
- 6.1k
- Forks
- 1.5k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 189
Description
Can we attach a UUID to each API operation so that tracing it becomes easier among the massive amounts of logs in servers/controllers? This would make tracing that operation very easy, compared to how it is right now. This would entail putting a UUID to the MDC and transferring it across threads and configuring log4j to log the key with every statement.
(There must be some reason to why this isn't being done right now which, if true, I am not aware of). Thanks!
Contributor guide
Research direction
Start by locating the API operation handling in the servers/controllers and reviewing how Log4j is configured. Investigate whether an operation UUID can be placed in MDC and transferred across threads without losing or mixing request context. Done means the UUID appears in logs for each API operation and the approach is covered by appropriate tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100