archiving task - log/report needed

I've asked this exact question.  The only partial answer I've heard is to run dtrace during the production run.  I haven't tried this because it seems like dtrace would dump out way too much information, but if you were very specific with which options you selected and didn't use verbose mode it might kind of work.

RANT - The ability to turn on tracing without bouncing services is nice, but it is not logging.  The event log is already "noisy", but still rarely has sufficient information to determine a problem's cause.  Immediately having to fall back to dtrace and attempting to recreate the problem is a poor substitute for proper logging.