Re: [prometheus-users] Clarifying jobs/targets/instances when monitoring multiple systems from a single Prometheus server

2021-03-04 Thread Stuart Clark
On 03/03/2021 17:18, John Dexter wrote: -- Stuart Clark Stuart, this is totally bespoke C++ Windows system,  none of those :) The file-discovery seems able to pull out my targets but I can't find a good example how to structure my files. I suppose each Module

Re: [prometheus-users] Clarifying jobs/targets/instances when monitoring multiple systems from a single Prometheus server

2021-03-03 Thread John Dexter
On Wed, 3 Mar 2021 at 14:41, Stuart Clark wrote: > On 03/03/2021 14:33, John Dexter wrote: > > > > On Wed, 3 Mar 2021 at 14:15, Stuart Clark > wrote: > >> On 03/03/2021 13:00, John Dexter wrote: >> > While I understand the technical definitions I would appreciate some >> > real-world advice in t

Re: [prometheus-users] Clarifying jobs/targets/instances when monitoring multiple systems from a single Prometheus server

2021-03-03 Thread Stuart Clark
On 03/03/2021 14:33, John Dexter wrote: On Wed, 3 Mar 2021 at 14:15, Stuart Clark > wrote: On 03/03/2021 13:00, John Dexter wrote: > While I understand the technical definitions I would appreciate some > real-world advice in the best way to str

Re: [prometheus-users] Clarifying jobs/targets/instances when monitoring multiple systems from a single Prometheus server

2021-03-03 Thread John Dexter
On Wed, 3 Mar 2021 at 14:15, Stuart Clark wrote: > On 03/03/2021 13:00, John Dexter wrote: > > While I understand the technical definitions I would appreciate some > > real-world advice in the best way to structure my configuration file > > for scalability and maintenance. > > > > Our system incl

Re: [prometheus-users] Clarifying jobs/targets/instances when monitoring multiple systems from a single Prometheus server

2021-03-03 Thread Stuart Clark
On 03/03/2021 13:00, John Dexter wrote: While I understand the technical definitions I would appreciate some real-world advice in the best way to structure my configuration file for scalability and maintenance. Our system includes many instrumented modules running on an application server on

Re: [prometheus-users] Clarifying jobs/targets/instances when monitoring multiple systems from a single Prometheus server

2021-03-03 Thread Jiacai Liu
Prometheus have support for k8s/marathon/zk based discovery, since you ask for monitoring method I assume you haven't used any of them. I think a (python)script that generate the file-based config is enough. On Wed, Mar 03, 2021 at 21:00 +0800, John Dexter wrote: While I understand the techni

[prometheus-users] Clarifying jobs/targets/instances when monitoring multiple systems from a single Prometheus server

2021-03-03 Thread John Dexter
While I understand the technical definitions I would appreciate some real-world advice in the best way to structure my configuration file for scalability and maintenance. Our system includes many instrumented modules running on an application server on distinct ports, e.g on APPSERVER001 modules [