temporalio / temporalio/temporal
Add programmatic way to extract metrics port when passing `0` in config
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.
When using the repo as a library, as in the cli, there's no good way (that I could find) to extract the bound metrics port if you pass in 0 in the config. This makes it hard to figure out (log, in my case) what port was actually chosen. I had to find a free port first to work around that, even though the code would do that for me.
Describe the solution you'd like
Have some easy way to fetch the chosen metrics port after instantiating / starting a dev server
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 file, test, or entry point. Start by tracing the metrics configuration and dev-server startup path, then identify how the selected port can be exposed to library callers. Done means callers can retrieve the actual bound port after starting with port 0.
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