Potentially Inconsistent TraceID Priority
Open
- Dominant language
- Go
- Stars
- 6
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
TraceID can exist in the RequestWithTraceID object, the Annotations, and the Status on the same reconcile.
We need to make sure these are consistently applied across all event handlers and starttrace/span functions.
Contributor guide
Research direction
Start by locating the event handlers and the starttrace/span functions that consume TraceID from RequestWithTraceID, Annotations, and Status. Compare their priority rules and check how the same reconcile behaves when multiple sources are present. Done means TraceID is applied consistently across all handlers and starttrace/span functions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100