On Thu, Dec 14, 2017 at 5:28 PM, Lukas Zapletal <[email protected]> wrote:
> Exactly, I based my proposal on Prometheus and Statsd. You can choose. > > I am going to work on my PR next week hopefully, but you can test it today: > > https://gist.github.com/lzap/2dfdd4dea29786a837cb1b7feb7862fd Don't you have a docker container somewhere all setup? ;) > > > Thanks for feedback! > > On Thu, Dec 14, 2017 at 3:52 PM, Tom McKay <[email protected]> wrote: > > Ooops! I should have watched your video first. :) Watching it now. > "Proposal > > to integrate Prometheus and Statsd instrumentation libraries into Foreman > > ..." > > > > On Thu, Dec 14, 2017 at 9:26 AM, Tom McKay <[email protected]> > wrote: > >> > >> Openshift uses Prometheus[1] which seems very similar and compatible > with > >> your ideas. Is that something you've looked at already? If/when foreman > is > >> containerized and perhaps run under kubernetes your work could be very > >> useful as well. > >> > >> https://blog.openshift.com/tag/prometheus/ > >> > >> > >> > >> On Fri, Nov 24, 2017 at 12:54 PM, Lukas Zapletal <[email protected]> > wrote: > >>> > >>> > 1. what happened to the PCP approach we talked about in the past? > >>> > >>> Thats going in parallel, PCP is just a monitoring framework you can > >>> integrate with instrumentation data just like any other. > >>> > >>> > 2. how would you integrate this to sosreport/foreman-debug? I'm > >>> > thinking of > >>> > storing the statsd data locally, collecting them with foreman-debug, > >>> > and > >>> > then, being able to import them later to the prometheus and other > >>> > tools. Is > >>> > this how this could work? Any other options? > >>> > >>> This is my ultimate goal to have working PCP deployment including > >>> telemetry data and archives could be collected by foreman-debug, they > >>> are pretty small (few MBs per day). > >>> > >>> > 3. does every host/runtime needs it's own statsd service, or there > >>> > would be > >>> > one shared process? Asking bith for multi-host and containers > use-case > >>> > >>> It is up to you if you want one statsd service per guest/container, > >>> host or subnet. Prometheus endpoint will not require any external > >>> daemon once sharing metrics is merged into upstream. For this reason, > >>> statsd will server as a temporary solution and alternative for the > >>> future. > >>> > >>> > The proposal of the telemetry api itself seems reasonable, let's > >>> > discuss > >>> > that on an actual PR > >>> > >>> Thanks, I hope to finish it this year. > >>> > >>> -- > >>> Later, > >>> Lukas @lzap Zapletal > >>> > >>> -- > >>> You received this message because you are subscribed to the Google > Groups > >>> "foreman-dev" group. > >>> To unsubscribe from this group and stop receiving emails from it, send > an > >>> email to [email protected]. > >>> For more options, visit https://groups.google.com/d/optout. > >> > >> > > > > -- > > You received this message because you are subscribed to the Google Groups > > "foreman-dev" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [email protected]. > > For more options, visit https://groups.google.com/d/optout. > > > > -- > Later, > Lukas @lzap Zapletal > > -- > You received this message because you are subscribed to the Google Groups > "foreman-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
