temporalio / temporalio/temporal
System search attributes to find workflows that are backoff retrying an activity
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
Is your feature request related to a problem? Please describe.
It’s hard to find out those workflows . The only way is through logs but sometimes logs are too noisy to read and search when production is running in outrage.
Describe the solution you'd like
Provide system search attributes like historyLength, eg retryingActivityType to help searching in webUI
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
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 defining the requested system search attributes, including historyLength and retryingActivityType, and how they should represent workflows whose activities are backing off for retry. Confirm how these attributes should support searching in the Web UI; the issue names no files or tests, so the implementation entry point and completion checks still need to be established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100