title: Prometheus with several servers
body: <p>I am starting to look at the Prometheus project and prototype it. So far I have implemented a few counters in my application (running on Weblogic), exposed the metrics servlet (dedicated war file), started on a dedicated machine a Prometheus server + Grafana using Docker images. Everything's working fine, the server scraps the counters and Grafana displays them in graphs.</p>
  
  <p>But I am facing an issue because of my runtime environment. Basically I target my application via <code>https://&lt;myserver&gt;/&lt;myproduct&gt;</code>, and target the metrics via <code>https://&lt;myserver&gt;/prometheus/metrics/</code>, but then behind the scene I can hit two different Weblogic servers, that are not exposed outside of the platform they are deployed in (so my machine hosting the Prometheus server cannot reach the Weblogic instances directly). So I get different metrics depending on the server that will chosen to be hit by the load balancer.</p>
  
  <p>Is there a way to workaround this kind of setup? A way to tell Prometheus server to aggregate the results somehow?</p>
  
  <p>Thanks for your help!</p>