The following tables contain synchronization statistics that
might appear in Operations, as well as descriptions for each of
those statistics.
Statistic |
Description |
Unchanged |
The object referred to by the change was looked up by the
anchor and found in the connector space with the same distinguished
name (also known as DN). By comparing attributes and values, it was
determined that its hologram in the connector space matches the
incoming change, which will result in no change. |
Adds |
The object referred to by the change was looked up by the
anchor and not found in the connector space. A new connector space
object was created with the information specified in this change.
If there is a connector space object with a different anchor and
the same distinguished name (also known as DN), the existing
connector space object will be moved into the transient state. This
transient move is not accounted for in the statistics. |
Updates |
The object referred to by the change was looked up by the
anchor and found in the connector space with the same distinguished
name (also known as DN). By comparing attributes and values, it was
determined that its hologram in the connector space is different,
implying that there is an update.
Note
- If there are multiple updates to a single object, then each
update will be reported in the counter total. When you click
Updates, Object Details contains an entry for each
update operation. However, each of the object properties displayed
will be of the object's current state.
|
Renames |
The object referred to by the change was looked up by the
anchor and found in the connector space, but the distinguished name
(also known as DN) is different. Staging a rename will cause the
distinguished name in the connector space to change and that can
trigger a move of an existing connector space object to a transient
state. This transient move is not accounted for in the
statistics. |
Deletes |
For delta import runs, the incoming change was a delete and the
object being deleted was found in the connector space. For full
import runs, either an incoming delete was imported and found in
the connector space or the object was obsolete. There is no
difference in the accounting of the two cases, but generally for
the management agents for Active Directory and Active Directory
Application Mode (ADAM) staging this counter indicates the number
of imported tombstones that corresponded to objects in the
connector space. |
Statistic |
Description |
Adds |
The count of new object creations that the management agent has
processed successfully or which have been written to the drop
file. |
Updates |
The count of object updates, which do not involve renames of
the object, that the management agent has processed successfully or
which have been written to the drop file. |
Renames |
The count of object updates, which do include renames of the
object, that the management agent has processed successfully or
which have been written to the drop file. |
Deletes |
The count of object deletes that the management agent has
processed successfully or which have been written to the drop
file. |
Delete Adds |
The count of modifications, which involve deleting the existing
object and adding a new object with the same distinguished name
(also known as DN), that the management agent has processed
successfully or which have been written to the drop file. |
Statistic |
Description (one or more of the following) |
Projections |
- The count of disconnectors that were projected for which there
was no actual import attribute flow to the metaverse.
- The count of disconnectors that were projected for which actual
attribute changes flowed to the metaverse.
- The count of disconnectors that tried to project to the
metaverse, but in the process the provisioning extension
programmatically disconnected connectors leading to the removal of
the metaverse object it was trying to create.
|
Joins |
- The count of disconnectors that were successfully joined for
which there was no actual attribute changes flowed to the
metaverse.
- The count of disconnectors that were successfully joined for
which actual attribute changes flowed to the metaverse.
- The count of disconnectors that joined to metaverse objects in
the first part of the synchronization process, but ended up
removing that metaverse object because the provisioning extension
programmatically disconnected its connectors.
|
Filtered Disconnectors |
- The count of disconnectors that were run through the connector
filter and marked as filtered disconnectors.
|
Disconnectors |
- The count of disconnectors that successfully passed the
connector filter test, but which there were no rules calling for
them to project or join and now remain as normal disconnectors in
the connector space.
|
Connectors with Flow Updates |
- The count of existing connectors that passed the connector
filter test and remained connectors. When import attribute flow was
applied, new or changed values were flowed to the metaverse.
- The count of disconnectors that were projected for which actual
attribute changes flowed to the metaverse.
- The count of disconnectors that were successfully joined for
which actual attribute changes flowed to the metaverse.
- The count of existing connectors that passed the connector
filter test and had import attribute flow applied to them, but had
their metaverse object removed because the provisioning extension
programmatically disconnected the connectors joined to that
metaverse object.
|
Connectors without Flow Updates |
- The count of existing connectors that passed the connector
filter test and remained connectors. When import attribute flow was
applied to these connectors, no actual attribute flow to the
metaverse occurred.
- The count of disconnectors that were projected for which there
was no actual import attribute flow to the metaverse.
- The count of disconnectors that were successfully joined for
which there was no actual attribute changes flowed to the
metaverse.
|
Filtered Connectors |
- The count of existing connectors which were disconnected by the
connector filter on this pass but the metaverse object was left in
place.
- The count of existing connectors which were disconnected by the
connector filter on this pass causing the metaverse object to be
removed.
|
Deleted Connectors |
- The count of existing connectors which were deleted on this
pass for which the metaverse object was left in place.
- The count of existing connectors which were deleted on this
pass for which the metaverse object was removed.
|
Metaverse Object Deletes |
- The count of disconnectors that tried to project to the
metaverse, but in the process the provisioning extension
programmatically disconnected connectors leading to the removal of
the metaverse object it was trying to create.
- The count of disconnectors that joined to metaverse objects in
the first part of the synchronization process, but ended up
removing that metaverse object because the provisioning extension
programmatically disconnected its connectors.
- The count of existing connectors that passed the connector
filter test and had import attribute flow applied to them, but had
their metaverse object removed because the provisioning extension
programmatically disconnected the connectors joined to that
metaverse object.
- The count of existing connectors which were deleted on this
pass for which the metaverse object was removed.
- The count of existing connectors which were disconnected by the
connector filter on this pass causing the metaverse object to be
removed.
|
Statistic |
Description (one or more of the following) |
Export Attribute Flow |
- The count of existing connectors that performed export
attribute flow for which there was actual attribute flow from the
metaverse to this object.
- The count of newly provisioned connectors that were added to
the connector space of this management agent for which there was
some actual export attribute flow from the metaverse to the
connector space (in addition to initial values the provisioning
script might have set at the time of provisioning).
- The count of provisioned renames during this run management
agent for which there was some actual export attribute flow from
the metaverse to the connector space.
|
Provisioning Adds |
- The count of newly provisioned connectors that were added to
the connector space of this management agent for which there was no
actual export attribute flow from the metaverse to the connector
space (although the provisioning script might have set some initial
values at the time of provisioning).
- The count of newly provisioned connectors that were added to
the connector space of this management agent for which there was
some actual export attribute flow from the metaverse to the
connector space (in addition to initial values the provisioning
script might have set at the time of provisioning).
|
Provisioning Renames |
- The count of provisioned renames during this run management
agent for which there was no actual export attribute flow from the
metaverse to the connector space.
- The count of provisioned renames during this run management
agent for which there was some actual export attribute flow from
the metaverse to the connector space.
|
Provisioning Disconnects |
- The count of provisioned disconnects during this run.
|
Provisioning Delete/Adds |
- The count of connectors that first provisioned a connector
delete, and then provisioned an add with the same distinguished
name (also known as DN) for which there was no actual export
attribute flow from the metaverse to the connector space (although
the provisioning script may have set some initial values at the
time of provisioning).
- The count of connectors that first provisioned a connector
delete, and then provisioned an add with the same distinguished
name (also known as DN) for which there was some actual export
attribute flow from the metaverse to the connector space (in
addition to initial values the provisioning script may have set at
the time of provisioning).
|