temporalio / temporalio/temporal
Adding sql metric stats
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.
Excessive connection created to PG
Describe the solution you'd like
Expose more SQL connection metrics from temporal, provide more insight when troubleshooting and config tunning
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 locating the SQL connection handling and existing metrics in the Temporal service, then review how PostgreSQL configuration and metric exposure are organized. The issue is complete when useful SQL connection statistics are exposed for troubleshooting excessive PostgreSQL connections and configuration tuning, with coverage for the new metrics.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, postgresql
- Domain
- backend, databases, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100