argoproj / argoproj/argo-workflows
Add `node` name to generated spans
- Dominant language
- Go
- Stars
- 17k
- Forks
- 3.7k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 138
Description
# Summary
The new tracing functionality for workflows is really nice 🚀 it would be even more useful if one could tell from a node span which template it executed (and, prospectively, also with which parameters etc.).
## Use Cases
- Investigating traces for workflows
---
**Message from the maintainers**:
Love this feature request? Give it a 👍. We prioritise the proposals with the most 👍.
Contributor guide
Research direction
No file or test is named in the issue. Start by locating the workflow tracing implementation that creates node spans and inspect how the node name and executed template are represented; done means generated node spans expose the node name for workflow trace investigation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100