temporalio / temporalio/sdk-java
Report replay metrics
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 433
- Forks
- 249
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 26
Description
Is your feature request related to a problem? Please describe.
We don't report the completion of workflows during replays. This is a good default behavior for these main completion counters, but we are lacking any reporting of replays counters.
Describe the solution you'd like
Replay metrics could be important for detecting the anomaly behavior of the system. We should discuss how do we want to report replays metric.
- Do we want to report them by status codes?
- Do we want to just report a total number of replays?
- Only full replays or partial too?
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
The issue names no files, tests, or entry points. Start by reviewing how replay completion is handled and how workflow metrics are reported; the work is done when the project decides whether to report total, status-based, full, and partial replay metrics and defines the chosen behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100