manticoresoftware / manticoresoftware/manticoresearch
Add native prometheus support to manticore daemon
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 12k
- Forks
- 642
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 47
Description
You recently published a docker based prometheus metric exporter tool using a dockerized php application.
While it works, I believe it would be much better if the manticore search daemon could be configured to enable prometheus metrics on port 9100 or similar.
The reasoning is that such solution wouldn't require an additional component to make the monitoring work, and the less moving parts would align better with the keep it simple philosophy.
Optionally it would be nice to have a whitelist of ip address(es) in the config file for the prometheus nodes to restrict access to the metrics url, eg.
`prometheus_hosts = 1.2.3.4/32,10.0.0.0/24` or something like that.
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
No files, tests, or entry points are named. First clarify the daemon configuration and endpoint design, including whether the optional prometheus_hosts whitelist is in scope; done means native Prometheus metrics are exposed by the daemon without the separate exporter.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, prometheus
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100