Maintaining an Identity Server 269novdocx (en) 19 February 201011.6.10 LDAPSuccessful PayloadExaminationsThe total number of successful payload examinations to identify theauthoritative server since the Identity Server was started.Identity ID Broadcasts The total number of attempted Identity ID Broadcasts to identify theauthoritative server since the Identity Server was started.Successful Identity IDBroadcastsThe total number of successful Identity ID Broadcasts to identify theauthoritative server since the Identity Server was started.Session ID Broadcasts The total number of attempted Session ID Broadcasts to identify theauthoritative server.Successful Session IDBroadcastsThe total number of successful Session ID Broadcasts to identify theauthoritative server since the Identity Server was started.Statistic DescriptionConnections Created The total number of LDAP connections created since the Identity Serverwas started. This count is a sum of all connections created to all replicasof the configuration data store and all user stores.Connections Destroyed The total number of LDAP connections destroyed since the Identity Serverwas started. This count is a sum of all connections destroyed on allreplicas of the configuration data store and all user stores.Connections Reused The total number of times an LDAP connection was reused for asubsequent administrative task since the Identity Server was started.Connections SharedBetween PoolsThe total number of times an LDAP connection count has been sharedbetween connection pools since the Identity Server was started. EachLDAP replica contains two connection pools: the user connection pool andthe administration connection pool. User connections are used to authenticate users and they arecreated and immediately destroyed. Administration connections are persisted in the pool and reused foradministrative tasks.Each pool has a maximum number of current connections it is allowed tohold at any one time. Initially, the number of allowed connections isallocated evenly between the two pools. If a much greater demand isdetected for one pool over the other, then the pools reallocate theirmaximum number of connections, increasing one pool's maximum by oneand decreasing the other pool's maximum by one. When this happens, it issaid that the pool “shared” a connection with the other pool.User Store Replica Restarts The number of times that a user store replica became unavailable suchthat a restart was necessary since the Identity Server was started. A userstore restart is attempted once every minute.Successful User StoreReplica RestartsThe number of times that a user store replica restart was successfullycompleted since the Identity Server was started.Statistic Description
