How to disable Prometheus when running couchbase as container
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 155
- Forks
- 154
- Avg merge
- 10h 45m
- Merged PRs (30d)
- 2
Description
When i ran the couchbase container using docker-compose, i found the CB is taking way too much CPU and noticed Prometheus and beam.smp process was taking roughly taking 700m CPU all the time.
I am wondering how we can disable Prometheus on containers, is there any environment flag that can be used to disable Prometheus.
Also, i noticed that there were about 60+ connections to the couchbase even after creating the container. Do Prometheus and other services use the connections to gather metrics? Is there any way we can trace the connections by source?
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 mentions Docker Compose, Prometheus, and Couchbase container connections but names no repository file, test, or entry point. Start by reproducing the reported CPU and connection behavior from the Docker Compose setup, then determine whether supported configuration or documentation addresses it; done requires a maintainer-confirmed answer.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, prometheus
- Domain
- devops, infrastructure, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100