Add tracing support in operator
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 608
- Forks
- 263
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 125
Description
Feature request
Currently we do not have tracing support to measure the time taken(latency and parameters used) on reconcile logic and other blocks. Without this trace, it is really hard to narrow down the performance related issues.
I see pipeline repository already has tracing support via https://github.com/tektoncd/community/blob/main/teps/0124-distributed-tracing-for-tasks-and-pipelines.md
Use case
On performance issue, I want to narrow down the latency, where it is happening.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading TEP 0124, the distributed-tracing design linked in the issue, then inspect the operator's reconcile logic and other blocks mentioned. The work is done when traces expose latency and parameters across the relevant paths well enough to locate performance bottlenecks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- backend, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100