temporalio / temporalio/features
Make metrics concerning unregistered activities (and maybe other things) consistent
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 32
- Forks
- 28
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 7
Description
Describe the solution you'd like
Make metrics concerning unregistered activities (and maybe other things) consistent across SDKs. Today Go has temporal_unregistered_activity_invocation, we need to do it across all SDKs. Also, consider adding metrics for other unregistered things (and confirm whether they exist in older SDKs).
Per-SDK Tickets
- Go -
- Java -
- Core -
- TypeScript -
- Python -
- .NET -
- Ruby -
- PHP -
- Temporal CLI - N/A
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
The issue names no files, tests, or SDK entry points. Start with the existing Go metric temporal_unregistered_activity_invocation, compare its behavior across the listed SDKs, and determine which other unregistered entities need metrics; done means the cross-SDK metric decisions and implementation scope are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, java, php, python, ruby, typescript
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100