The MindLink Server exposes a custom suite of Windows performance counters that can be used to monitor the usage and health of the system. The performance counter suite can be used to indicate general usage statistics as well as to detect outages or other problems, via the number and rate of errors thrown.
Saving the management tool automatically adds the service account to the local Performance Logs Users group.
In addition, the MindLink server is a .NET service and hence exposes the standard suite of .NET performance counters. It is recommended to monitor at least the standard Windows memory usage and CPU performance counters, as well as the MindLink performance counters that report error rates, as a general indication of service health.
The category in which the MindLink performance counters are found is called 'CollaborationFoundation'.
Tools such as Microsoft's Performance Monitor (perfmon.exe) can be used to view the value of the counter and generate reports. A performance counter can be added by clicking the green plus icon in the performance monitor.
The collaboration foundation entry has a dropdown which contains the performance counters.
Select the performance counter needed and then select the instance of the object, click 'Add' and then confirm by clicking 'OK'.
Below is an example of how the performance counter appears in the performance monitor when selected.
Please note, to view Performance Counters from a remote computer the Performance Logs and Alerts firewall exception must be enabled on the remote computer.
MindLink Performance Counters
The performance counters and how they are updated are as follows:
|Bytes Downloaded Per Second||MLA/MLM/MLAPI|
|Bytes Uploaded Per Second||MLA/MLM/MLAPI|
|Exchange Web Services Calls||MLA/MLM/MLAPI|
|Exchange Web Services Calls Per Second||MLA/MLM/MLAPI|
|File Downloads Per Second||MLA/MLM/MLAPI|
|File Uploads Per Second||MLA/MLM/MLAPI|
|Group Id Lookups||MLA/MLM/MLAPI|
|Group Id Lookups Per Second||MLA/MLM/MLAPI|
|Group Searches Per Second||MLA/MLM/MLAPI|
|History Searches Per Second||MLA/MLM/MLAPI|
|Remote Group Joins||MLA/MLM/MLAPI|
|Remote Group Joins Per Second||MLA/MLM/MLAPI|
|Remote Group Leaves||MLA/MLM/MLAPI|
|Remote Group Leaves Per Second||MLA/MLM/MLAPI|
|Messages Received Per Second||MLA/MLM/MLAPI|
|Messages Sent Per Second||MLA/MLM/MLAPI|
|Metadata Updates Per Second||MLA/MLM/MLAPI|
|Preferences Saves Per Second||MLA/MLM/MLAPI|
User Services Performance Counters:
|Active Persistent Connections||MLA/MLM|
|Active Presence Subscriptions||MLA|
|Mobile Session Event Filter Percentage||MLM|
|Push Data Sent||MLM|
|Push Messages Sent||MLM|
|Socket Data Received||MLM|
|Socket Messages Received||MLM|
|Socket Messages Sent||MLM|
|Total User Information Requests Calls||MLA|
Translation Performance Counters:
|Average Translation Service Request Time Seconds||MLA/MLM/MLAPI|
|Failed Translation Service requests||MLA/MLM/MLAPI|
|Failed Translation Service requests Per Second||MLA/MLM/MLAPI|
|Translation Service Bytes Downloaded||MLA/MLM/MLAPI|
|Translation Service Bytes Downloaded Per Second||MLA/MLM/MLAPI|
|Translation Service Bytes Uploaded||MLA/MLM/MLAPI|
|Translation Service Bytes Uploaded Per Second||MLA/MLM/MLAPI|
|Translation Service Requests||MLA/MLM/MLAPI|
|Translation Service Requests Per Second||MLA/MLM/MLAPI|
There are global performance counters for authentication as well as performance counters specific to each authentication mechanism (Password, Windows and HTTP Header Authentication). Each global performance counter listed below has a similar counter specific to the authentication mechanism in use.
|Average Authentication Request Time Seconds||MLA/MLM/MLAPI|
|Authentication Requests per Second||MLA/MLM/MLAPI|
|Failed Authentication Requests||MLA/MLM/MLAPI|
|Failed Authentication Requests Per Second||MLA/MLM/MLAPI|
|Last Authentication Time Taken Milliseconds||MLA/MLM/MLAPI|