Shows what actions were executed. Currently there are only basic actions (ADD, MODIFY, DELETE) carried out on
basic categories of objects (object types, e.g. UserType, RoleType, OrgType, ShadowType, ...).
This gives a quick overview what e.g. import, livesync or reconciliation task is really doing.
For example, if it really creates new users, or if it deletes anything, etc.
Two categories of statistics are described: "all" and "resulting".
The former describes all operations carried out, whereas the latter describes only the "high-level" or "externally visible" ones.
An example: if a live sync task detects a new resource objects, creates appropriate user, and modifies it twice (because of
outbound/inbound/template/etc interplay), the "all" category would contain 1xADD and 2xMODIFY for that user. However,
the "resulting" category shows what the external observer would expect - that 1 user was added (so, 1xADD).
Note that the behavior of "resulting" action determination is still experimental, and need to be specified more
precisely, e.g. with regards to operation failures.
In future it would be nice to distinguish e.g. between shadows on different resources.
Also, the semantics of operations on ShadowType should be defined more precisely - namely,
whether an operation means "operation on repository shadow" or "operation on resource object".
Currently, it means both of them. And some of the shadow related operations are not counted,
namely those that are carried out autonomously by the provisioning module - e.g. creating repo
shadows when resource objects are discovered. Also, displaying the result of operations that
are handled by consistency mechanism is defined quite well.
Overall, while counters related to focal objects (users, roles, orgs) are relatively well defined,
counters related to shadows need some clarification.