[chef] Re: Re: Poor man's reporting.

[Nathen Harvey < >]

Sorry, are you asking how to write custom ruby code without having to read any ruby?

I'm afraid that's not a path toward anything like success.   

There are a number of handlers available on the Supermarket and GitHub that you might be able to configure without needing to write much more than some configuration. 

Of course, hosted Chef and Enterprise Chef running on premise both include reporting features out-of-the-box, too. 

If you truly want a "poor man's solution," that's customized exactly as you like, it's going to require an investment. 

Research and try some of the available solutions to see if they suit your needs. If not, you'll likely have to read and experiment with some ruby. 

Good luck!
--

Nathen Harvey

On Aug 18, 2014, at 5:25 PM, Douglas Garstang < "> > wrote:

Nathan,

Can a handler be configured to call a URL when there's no failure? Would like to record the start time. Also, do handlers have to be email, or can I use a GET to a URL instead upon failure?

Code... ruby... oh...  Are there any good docs on handlers that don't involve reading ruby code?

Doug.

On Mon, Aug 18, 2014 at 2:20 PM, Nathen Harvey < " target="_blank"> > wrote:

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

--
Regards,

Douglas Garstang
http://www.linkedin.com/in/garstang
Email: ">
Cell: +1-805-340-5627