[chef] Re: Re: Notification of changes to non-node Chef server data

[Kevin Counts < >]

One possibility would be to run a knife backup export on a regular basis to a time-stamped directory, then have a job run a recursive diff to detect any changes.

You can also run knife diff against the server comparing whats in your local repository and find discrepancies but this doesn't diff nodes which are usually only in chef server.

Nginx logs definitely show puts, posts, etc. but don't have any offhand suggestions on parsing methods for that - to me, although depending on the size of your instance may take some time, comparing knife backup exports seems like a start.

On Tue, Sep 3, 2013 at 10:49 AM, Jeff Blaine < " target="_blank"> > wrote:

On 8/29/2013 4:42 PM, Jeff Blaine wrote:

How are others going about being notified of changes (and their
contents/diffs) to a Chef server? Perform Big Data Agile
SplunkStash Analytics HadoopStormStash on the Erchef log?

Nobody's keeping track of what changed in the Chef server data store
and who changed it?

--
Kevin Counts < "> >