On Tuesday, September 26, 2017 at 3:42:46 PM UTC+10, Ben Kochie
wrote:
> If the individual daemons are their own separate services, the intended design is that they each report their own metrics. The multi-process mode is for identical worker processes behind a single master request router.
>
>
> On Tue, Sep 26, 2017 at 7:00 AM, <
haroldj...@gmail.com> wrote:
> Hi list (or Brian)
>
> I am looking to instrument an app with multiple daemons.
>
> Can the multiprocessing code be used for that?
>
> I don't truly understand the multiprocessing instructions but would like to expose all the instrumentation from a single port/http server and it doesn't look like other daemons can report without their own http server.
>
>
>
> --
>
> You received this message because you are subscribed to the Google Groups "Prometheus Developers" group.
>
> To unsubscribe from this group and stop receiving emails from it, send an email to
prometheus-devel...@googlegroups.com.
>
> To post to this group, send email to
prometheus...@googlegroups.com.
Thanks Ben
The separate daemons are part of the same application and maybe some would logically be separated but not all. I have not read the source but I guess I'd be looking for how something like the counter populates the data so that I can populate instrumentation objects in separate daemons. Perhaps some attribute of the start_http_server?