How to know chef-client run start and end time

Chef Infra (archive)
1

hi,

How to know chef-client start and End time once it was run?
How to know single cookbook or multiple cookbook execution start and end time?

Thanks and Regards,
Ganesan.A

2

The client.log file (found in /var/log/chef on a Linux machine) should have
the start and end times of all your chef-client runs.

On Wed, May 7, 2014 at 3:19 AM, ganesan15785@gmail.com wrote:

hi,

How to know chef-client start and End time once it was run?
How to know single cookbook or multiple cookbook execution start and end
time?

Thanks and Regards,
Ganesan.A

3

I'm pretty sure all the information you're looking for is exposed to the
report handler plugins at the end of the chef run. There is also an
existing profiler report handler that might do the trick for you. If not,
it should be pretty clear based upon how it's implemented to get the
information you're looking for.

Hope this helps!

On Wed, May 7, 2014 at 7:52 AM, Fabien Delpierre <fabien.delpierre@gmail.com

wrote:

The client.log file (found in /var/log/chef on a Linux machine) should
have the start and end times of all your chef-client runs.

On Wed, May 7, 2014 at 3:19 AM, ganesan15785@gmail.com wrote:

hi,

How to know chef-client start and End time once it was run?
How to know single cookbook or multiple cookbook execution start and end
time?

Thanks and Regards,
Ganesan.A

4 
    How to know chef-client start and End time once it was run?
    How to know single cookbook or multiple cookbook execution start
    and end time?

Use the lastrun_update report handler that comes with 'knife-lastrun'.
It will store a chunk of info on each node object out on the chef
server, including success/failure, start time, end time, elapsed time,
resources updated, any exceptions if failure, etc.

See: GitHub - jgoulah/knife-lastrun: A plugin for Chef::Knife which displays node metadata about the last chef run.

I nominate this handler for "Most useful least known Chef code"

Jeff Blaine