Help deciphering AUSST logs?

Question

Hello,
I was wondering if someone could help me decipher the AUSST logs? I am required to report to our IT department all update activity for my systems (OS and apps) quarterly, including total file size. All the information I need is in the logs, but it's unclear what AUSST is actually doing.
I recently did an incremental update and decided to look at the logs to see if I could tell what kind of activity is actually going on in my Cache directory. The log entries seem to be self-explanatory but they don't agree with the response from the AUSST tool, or with the actual directory activity.
For instance; today's update claimed 1078 items were processed and there were errors in 0 items...
Processed 1078 out of 1078 items.
Error in 0 items.
AdobeUpdateServerSetupTool returned with code: 0.
For more information refer AdobeUpdateServerSetupTool.log at /Users/admin/Library/Logs .
However there are 3,345 entries in the log for today's update. That suggests there are roughly 3 log entries per "Item" processed by AUSST? What is an "Item?"
Also, when I search for items in my AUSST cache that have been created or modified during the last 12 hours, there are 1,224. That is more than the 1,078 "Items" and fewer than the 2,451 log entries that claim an item was downloaded.
I need this data to be accurate, but the logs and reality don't quite mesh so I think I must not understand the logs correctly.
Little help?
-Brian

Answer 1

Wait... bonehead move on my part. I forgot I had ran the update twice by accident so the log I was looking at (for todays date) actually had two complete cycles in it.
In this case, the number of files actually created or modified during the last 12 hours matches the number of entries in the log exactly. So that's the answer.
Also, if I look at distinct directories, I get 1078... exactly the number of "Items" processed by AUSST. So it appears when there are multiple files for a given "Item" they are not included in the count.
Okay, I think I get it now. If you have anything to add, please feel free, but I think I have all I need for my reporting purposes now.
-Brian