prometheus-community / prometheus-community/PushProx

Target Exporter on another machine

Open
#103 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
811
Forks
154
PR merge metrics
No merged PRs in 30d

Description

Hello Guys,

i'm trying to set up, a prometheus monitoring stack, that gathers information from different networks. Therefore i tried to installl one central proxy and a proxy client in each of the networks. That works fine so far, if i try to scrape exporters which run at the same machine as the client is running. Is it possible to target exporters on another machine in the same network via the agents, if yes how would i configure that. If no is the solution to host a proxy in each of these networks and a client on each machine i want to scrape exporters from?

Best regards
Andi

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the PushProx agent and proxy configuration documentation to determine whether an agent can reach exporters on other machines in its network. Confirm whether the requested topology is supported and document the required configuration, or state whether separate proxies are needed.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, prometheus
Domain
networking, observability-sre
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.