[chef] Re: Poor man's reporting.

[Nathen Harvey < >]

Chef Handlers are absolutely what you want.

Might be best to start with an existing handler and read through that code.  I find that the code can sometimes be even more informative than docs.

There are a couple of handlers listed on the Supermarket including the Chef Elapsed Time Handler.

Good luck!

Nathen

On Mon, Aug 18, 2014 at 5:17 PM, Douglas Garstang < " target="_blank"> > wrote:

I was trying to implement a poor mans chef reporting. I had the idea of putting this in a recipe to be run first in the run list:

response = Net::HTTP.get_response(URI.parse("http://server?action="start&host=#{node.fqdn}"))

....  and then putting this in a recipe to be run at the end of the run list:

response = Net::HTTP.get_response(URI.parse("http://server?action="end&host=#{node.fqdn}"))

I would then write a simple web service that would listen and put entries into a database. I noticed however that the URL to be called at the end of the run is executed before resources that were notified with 'delayed' were run, since they always run at the end of a chef run.

So... is there a way to execute something categorically at the end of a chef run? I've tried reading the handler docs but I just can't follow them.

Doug