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.
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.
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.
Never tried it myself, but sends the same basic reporting data that enterprise chef gets to a 3rd party reporting service (that you’ll need to set up and maintain).
--
Daniel DeLeo
On Monday, August 18, 2014 at 2:21 PM, Ranjib Dey wrote:
chef server enterprise edition has this baked in. for hook at the end or chef run , you can use report handlers or event handlers, any of those.
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.
Never tried it myself, but sends the same basic reporting data that
enterprise chef gets to a 3rd party reporting service (that you’ll need to
set up and maintain).
--
Daniel DeLeo
On Monday, August 18, 2014 at 2:21 PM, Ranjib Dey wrote:
chef server enterprise edition has this baked in. for hook at the end or
chef run , you can use report handlers or event handlers, any of those.
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.