Integrate the transaction sample with the debugTransaction feature
- Dominant language
- C++
- Stars
- 16.7k
- Forks
- 1.6k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 126
Description
From a NativeAPI transaction, it is possible to set an option for every server involved with processing that operation to log a trace event. This provides visibility into the amount of time it took to complete each step involved with the processing the transaction.
The transaction sample keeps latencies of client operations. If we combine these together, we could have much more detailed latencies in the transaction sample.
Contributor guide
Research direction
The issue names the transaction sample, NativeAPI transactions, and the debugTransaction feature; begin by locating those components and understanding how client latencies and server trace events are handled. Confirm the combined latency format and validation criteria with maintainers first, since no files, tests, or concrete output requirements are specified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- databases, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100