[multi stage] Measure threadCpuTime metric (similar to existing engine) in the operators, aggregate and include in response
- Dominant language
- Java
- Stars
- 6.1k
- Forks
- 1.5k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 189
Description
In the current engine, we measure threadCpuTime metric at the BaseCombineOperator level. Aggregated metric is sent to servers and broker aggregates across servers and includes in query response stats. We need to do something similar (granularity etc to be discussed) in the multi-stage engine.
Contributor guide
Research direction
Start by reading the existing threadCpuTime measurement at BaseCombineOperator and tracing how metrics move through the current engine, servers, broker, and query response stats. Compare those entry points with the multi-stage engine operators; the work is done when the agreed granularity is measured, aggregated across servers, and included in the response statistics.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, distributed-systems, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100