hello, ----- Original Message ----- > From: "Romain F." <romain.fi...@gmail.com> > To: "puppet-dev" <puppet-dev@googlegroups.com> > Sent: Friday, May 22, 2015 8:20:16 AM > Subject: [Puppet-dev] Adding metrics in agent report - PUP-4634
> Hi everyone, > Following the suggestion of Henrik L. we'll continue the discussion of > PUP-4634 here. > It began with my suggestion of adding some timings in agent code in order > to check steps which can take some time. And, thus, being able to > troubleshoot pretty ugly things like this : > > Info: Caching catalog for bulbi1.c-bulbi.tgcc.ccc.cea.fr in 6.48 seconds > Info: Convert catalog in 6.18 seconds > Info: Applying configuration version '1432224909' > ... > Notice: Finished catalog run in 88.45 seconds these would be good to add to both last_run_summary.yaml and the reports indeed, I mentioned this in the ticket but the report already contains a wealth of perf data, I have a report parser you can use on the CLI that produce output like this: https://github.com/ripienaar/puppet-reportprint/blob/master/SAMPLE.txt So already there you have config retrieval for example, adding more metrics around the saving and re-loading of the catalog would be handy. As well as firming up the docs around these and explain exactly what they are - this might exist now but last time I checked it didnt and it was a bit of guess work what they all do and mean esp some in last_run_summary.yaml. > Notice: Send report in 11.17 seconds obv this could not be in the report but be handy in last_run_summary.yaml It would be ideal if like the existing agent perf data this is always collected and always stored in reports but optionally shown to the console. I can't right now think of specific additions but whoever implements it should just go through every major life cycle event and make sure its reported. One thing that might be handy is some details around the number of HTTP requests that are being made to measure and observe the impact of things like the HTTP connection pool. -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/1091119205.46622.1432299184341.JavaMail.zimbra%40devco.net. For more options, visit https://groups.google.com/d/optout.
