temporalio / temporalio/features
Add metric for payload size for input/output/signal of workflow/activity
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 32
- Forks
- 28
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 7
Description
Is your feature request related to a problem? Please describe.
Temporal enforce 2MB size limit by default. But it would be too late when users run into this.
It will be better to let user set up a monitor on the size with a lower threshold like 1MB -- when something go beyond, they can start working on improving the applications or re-design it.
Describe the solution you'd like
Add a metric like history_event_payload_size
Describe alternatives you've considered
NA
Additional context
NA
Contributor guide
No contributing guide indexed for this repository
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
Use the proposed metric name, history_event_payload_size, as the search entry point; the issue does not mention implementation files or tests. Clarify how workflow and activity input, output, and signal sizes should be measured, then verify that the resulting metric supports a lower monitoring threshold.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100