prometheus-community / prometheus-community/postgres_exporter
memory usage: use of 100% of available RAM
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 3.6k
- Forks
- 835
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 10
Description
What did you do?
We have a postgres-exporter as a service in a Docker Swarm stack
What did you expect to see?
We do not expect container to always reach 100% of RAM in few days
What did you see instead? Under which circumstances?
With prometheus query
(container_memory_working_set_bytes{image!="", container_label_com_docker_swarm_service_name="opencity-aspsr_postgres-exporter"} / (container_spec_memory_limit_bytes{image!=""} > 0) * 100)
we see a steady upwards slope in memory usage: postgres-exporter is gradually consuming all memory over time.
Environment
We have a Docker Swarm service with image:
quay.io/prometheuscommunity/postgres-exporter:v0.17.1
-
postgres_exporter version:
v0.17.1
-
postgres_exporter flags:
none
-
PostgreSQL version:
image: 'postgres:14.17-alpine'
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 report names no source file, test, or entry point. Start by reproducing the steady memory increase for postgres-exporter v0.17.1 in the described Docker Swarm setup and monitoring it with the supplied Prometheus query; done means identifying the cause and verifying that memory no longer grows without bound.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go, postgresql
- Domain
- databases, infrastructure, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100