Add ability to view traces inside tilt
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10.1k
- Forks
- 413
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 6
Description
To improve observability it will be good to have integrations with popular tracing solutions like Jaeger and Zipkin.
Right now I see it something like this:
New tab in tilt's UI called traces, which can be something like recent grafana tracing viewer. Ability to go throughout all traces is not necessary, better have clickable trace IDs inside app's logs.
Traces can be fetched from tracing agent inside k8s cluster via REST API calls. We can fetch only traces that appears in logs or all traces from the agent. Tracing agent must be separate for a stand (for example it can be spun up with help of tilt extensions).
Ability to share traces with snapshots is also important, because traces can add a lot more context to help with debugging.
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
No files, tests, or entry points are named. Start by locating Tilt's UI, log, snapshot, and Kubernetes extension integration points, then clarify the trace-provider and trace-ID requirements; done would include an agreed scope for viewing and sharing traces.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, grafana, kubernetes
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100