Provisioning Logs: Counts seem to be expected changes

We had an Active Directory Provisioning problem where an error-logging line threw an unexpected RuntimeException and, therefore, crashed out the provisioner's Full Sync. This Jira is not about this Exception nor the provisioner's resilience to logging exceptions; I don't think it's worth the trouble to catch problems with logging. Instead, this Jira is about how the Daemon Log was confusing while the provisioner had this problem....

Every FullSync's daemon log for weeks showed thousands of changes into and out of our Active Directory. The top half of this screen shot is after the logging problem was fixed >10-18 05:17, and the bottom half shows the problem.

We believe that the 4000ish adds and 4000ish deletes were never actually happening, but were instead the expected changes based on comparing Grouper to the Target System. We were very confused and chasing ghosts for a good while. Additionally, the Activity Log didn't show any activity so we doubted it as well.

This report is requesting that the counts be a tabulation of actual changes made and anticipated changes. Perhaps the expected counts could be log4j-logged, but the Changes Made numbers in the Daemon Log should be correct.