prometheus-community / prometheus-community/PushProx
more complete configuration examples
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 811
- Forks
- 154
- PR merge metrics
- No merged PRs in 30d
Description
I've wrestled with wrapping together nginx for ssl wrapping, pushprox-proxy and -client; there apparently are some landmines that I am dancing on, but as there is no audible feedback like in real life, I have hard time telling when and where I took wrong turn.
Testing with curl:
proxyhost -> proxyclient/proxyclienthost: metrics about pushprox-client
proxyclienthost -> proxyclient/proxyclienthost: metrics about pushprox-client
proxyclienthost -> node_exporter/proxyclienthost: actual metrics
On startup, the pushprox-client manages to register with pushprox-proxy, but the garbage collection cycle cleans up the registration after a while. No actual data seems to be transmitted from node_exporter anywhere.
It would be really useful to have complete working configuration example as a starting point. Also, I would expect loglevel "debug" being at least slightly more verbose than "info", preferrably being very verbose on what the software is currently doing, what is failing and why.
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 the nginx, pushprox-proxy, pushprox-client, and node_exporter arrangement described in the issue, reproducing the listed curl paths and registration cleanup behavior. Done means a complete working configuration example is documented and debug logging makes failures and current activity more understandable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, nginx
- Domain
- documentation, networking, observability
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100