prometheus-community / prometheus-community/postgres_exporter
Improve pg_postmaster collector
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 3.6k
- Forks
- 835
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 10
Description
Proposal
Use case. Why is this important?
The pg_postmaster collector was ported from the queries.yaml file to a builtin collector in #801. This collector may need a larger discussion about how it should work. This issue is to track those changes and discussions.
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
Start with collector/pg_postmaster.go and the porting context in issue #801. Review how the pg_postmaster collector was moved from queries.yaml, then follow the discussion to define its intended behavior. Done requires agreement on the collector changes and implementation of that agreed design.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, postgresql
- Domain
- databases, observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100