[Improvement] Expose KyuubiOperation exec time metrics
- Dominant language
- Scala
- Stars
- 2.4k
- Forks
- 1k
- PR merge metrics
- No merged PRs in 30d
Description
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
### Search before asking
- [X] I have searched in the [issues](https://github.com/apache/kyuubi/issues?q=is%3Aissue) and found no similar issues.
### What would you like to be improved?
Kyuubi already supports `ExecuteStatement` exec_time metrics. If `KyuubiOperation` (`LaunchEngine`, `ExecutedCommandExec`) supports exec_time metrics, it will be more convenient when troubleshooting.
### How should we improve?
`KyuubiOperation` (`LaunchEngine`, `ExecutedCommandExec`) supports exec_time metrics
### Are you willing to submit PR?
- [X] Yes. I would be willing to submit a PR with guidance from the Kyuubi community to improve.
- [ ] No. I cannot submit a PR at this time.
Contributor guide
Research direction
Start by comparing the existing ExecuteStatement exec_time metrics with the KyuubiOperation components named in the issue: LaunchEngine and ExecutedCommandExec. Trace how those operations expose metrics, then verify that both report exec_time consistently for troubleshooting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100