Groove Server Relay statistics reference
Applies to: Groove Server 2010
Topic Last Modified: 2010-03-09
This article describes the statistics and related information that are provided in the Groove Server 2010 Relay administrative Web pages. Server administrators can use this information for maintaining the ongoing health of Relay servers and to troubleshoot problems. The tables in this article include descriptions for the most-useful Relay server statistics and related information.
For information about how to access the Relay server administrative Web pages, see Monitoring Groove Server Relay.
In this article:
Relay server statistics
SharePoint Workspace client accounts
SharePoint Workspace client bandwidth usage
SharePoint Workspace client devices
SharePoint Workspace device index
SharePoint Workspace user identities
Relay server queues
Relay server queue stores
Relay server users
Relay server connections
Relay serer trace logs
Relay server Event Log
Relay server database purges
Relay server queue reports
Refresh Relay server configuration values
Relay server statistics
The Statistics link on the Groove Server 2010 Relay administrative Web page displays Relay server statistics, as summarized in the following table. Most of these statistics also appear as counters in the Windows Performance Monitor (as described in Monitoring Groove Server Relay).
| Relay Statistics | Description |
|---|---|
| General Statistics: | |
| Start Time | The date and time when the Relay server started up. Indicates any rebooting/restarting activity, including automatic restarting of the service. |
| Build | The installed Relay server version information. |
| Queue/Store Statistics: | |
| Open Queues | The number of active (or open) queues on this server. |
| Total Queues | The number of queues stored on this server. For more information about Relay server message queues, see Managing Groove Server Relay databases. |
| FFQAppendMessegesPerSec | The total number of messages per second being received and enqueued by the Relay server. |
| FFQGetNextMsgsPerSec | The total number of messages per second being dequeued and sent by the Relay server. |
| Summary Connection Table: | |
| DevicesOnline | The number of client devices that are currently connected to the Relay server. This number includes devices that are only enqueueing data, and also clients for whom this is the primary Relay server. |
| UsersOnline | The number of logged-in Groove users assigned to this Relay server (via the Groove Manager) that have attached to this Relay server. |
| Connections | The sum of HTTP and SSTP connections to the Relay servers. |
| SSTP Connection Table: | |
| SSTP connections | The number of current SSTP connections. These connections remain open as long as the devices are connected to the relay. |
| HTTP Connection Table: | |
| HTTP connections | The number of current HTTP connections. These connections persist only long enough to transfer a message. Higher than usual numbers may indicate Relay server processing slowing down. Note: In SSTP (Groove’s native protocol), transfers are made using TCP port 2492 or 443. As long as a user is online, a connection is maintained with the user’s home Relay server. If, because of firewall or proxy issues, a client must connect via SSTP encapsulated in HTTP (TCP port 80), no long-term connection is maintained, and a client connection lasts only long enough for a single message enqueueing or dequeueing operation. Therefore, the HTTP Connections statistic can be highly variable, depending on user logon intervals. |
| RelayToRelayConnectionsOutCurrent | The current number of network connections between the reporting Relay server and foreign Relay servers. These connections were initiated by the reporting Relay server. |
| RelayToRelayConnectionsInCurrent | The current number of network connections between the reporting Relay server and foreign Relay servers. These connections were initiated by the foreign Relay servers. |
| OutboundRelayToRelayConnectionsFailedDNS | The number of times that the reporting Relay server attempted and failed to resolve a foreign Relay server’s Fully Qualified Domain Name with the Domain Name Service. A non-zero value may indicate a network infrastructure problem with DNS lookups which can cause network communication failures between Relay servers. |
| OutboundRelayToRelayConnectionsUnreachable | The number of times the reporting Relay server failed to establish a connection with a Foreign Relay. A steadily increasing value may indicate a network configuration issue that results in communication failures between Relays. |
SharePoint Workspace client accounts
The Accounts link on the Relay server administrative Web page lists SharePoint Workspace user accounts on the Relay server. From this accounts list page, you can click an account or enter an account URL in the Lookup text box to view detailed information about a specific identity, as described in the following table:
| Account statistics | Description |
|---|---|
| Account Information: | |
| URL | The globally unique URL of the SharePoint Workspace client account. |
| Name | The GUID piece of the SharePoint Workspace client account URL. |
| Relay | The Relay server name supplied by the device during client logon. |
| User | The globally unique URL of the managed identity for this account. |
| Attached | The account is connected and logged in to the Relay server. |
| Locked Out | Specifies if the account is blocked from using this Relay server. Account lockout occurs when an administrator uses the Groove Manager to lock out a managed identity. |
| Account Devices | URLs of Device Presence Protocol (DPP) devices supporting this account. To view details on a device (as described in Configuring Groove Server Relay bandwidth usage statistics), click the device identifier. |
| Account Identities | URLs of identities created in this account. To view details on an identity (as described in SharePoint Workspace client devices), click the identity information. |
| Account Security Information: | |
| Key Length | The length in bytes of the account-relay secret key, if any. |
| Token Length | The length in bytes of the account security token, if any. |
| Certificate Length | The length in bytes of the account certificate, if any. |
SharePoint Workspace client bandwidth usage
The Bandwidth link on the Relay server administrative Web page displays bandwidth usage samples taken at prescribed intervals for devices contacting the Relay server. Relay bandwidth statistics reflect the bandwidth (bytes per second) used by SharePoint Workspace client devices enqueueing and dequeueing data on the Relay server over a specific time interval. From this bandwidth page, you can click a device sample to view detailed information about a specific identity, as described in the table for this section. The Lookup text box lets you specify the maximum number of devices for which to display information.
The reporting of bandwidth usage statistics is a Relay server feature that is enabled or disabled through a Windows registry setting. The feature is enabled by default. For information about how to configure bandwidth usage statistics, see Configuring Groove Server Relay bandwidth usage statistics.
The following table summarizes bandwidth usage statistics:
| Bandwidth usage statistics | Description |
|---|---|
| Enter the top number of devices to display: | Accept the default of 25 to display bandwidth usage statistics for up to 25 SharePoint Workspace client devices per page, or enter another value in this field. Then click the Lookup button to display bandwidth usage for each SharePoint Workspace client device registered with the Relay server, up to the number that is specified in this field. The list of devices appears in descending order of bandwidth usage. The values on this page represent the bandwidth used by each device enqueueing and dequeuing on this Relay server since the last polling interval, or since server startup. To view detailed statistics for a selected device, click the device. Two groups of statistics appear, as follows: General bandwidth usage - Displays average bandwidth usage for all device activity, followed by separate average, maximum, and minimum usage values for enqueuing and for dequeuing, as described in this table. Detailed bandwidth usage - Displays average, maximum, and minimum bandwidth usage for dequeuing, as described later in this table. To disable this statistic, you add a new value to the Windows registry, as described in Configuring Groove Server Relay bandwidth usage statistics. |
| General Bandwidth Usage (Bytes/Sec) Since Last Poll: | |
| Average Bandwidth Usage | The average bandwidth in bytes per second used by the selected device to enqueue and dequeue SharePoint Workspace data on the Relay server since the last poll. The Relay server totals the bandwidth usage for each enqueueing or dequeueing device over a polling interval. Samples are collected from this interval and averaged to produce the average bandwidth. The Relay server calculates this value from samples collected between the last polling interval (or server startup if less than the last polling interval) and the Lookup time. The default polling interval is 2 minutes. The default sample interval (size) is 2 seconds. You can change the sample and polling intervals in the Windows registry, as described in Configuring Groove Server Relay bandwidth usage statistics. |
| Average Enqueue Bandwidth Usage | The average bandwidth used by the selected device to enqueue SharePoint Workspace data on the Relay server since the last poll. |
| Maximum Enqueue Bandwidth Usage | The maximum bandwidth used by the selected device to enqueue SharePoint Workspace data on the Relay server since the last poll. Maximum bandwidth is the largest sample value collected between the last polling interval (or server startup) and the Lookup time. See the description of Average Bandwidth Usage, earlier in this section, for more information about polling. |
| Minimum Enqueue Bandwidth Usage | The minimum bandwidth used by the selected device to enqueue SharePoint Workspace data on the Relay server since the last poll. Minimum bandwidth is the smallest sample value collected between the last polling interval (or server startup) and the Lookup time. See the description of Average Bandwidth Usage, earlier in this section, for more information about polling. |
| Average Dequeue Bandwidth Usage | The average bandwidth used by the selected device to dequeue SharePoint Workspace data on the Relay server since the last poll. |
| Maximum Dequeue Bandwidth Usage | The maximum bandwidth used by the selected device to dequeue SharePoint Workspace data on the Relay server since the last poll. Maximum bandwidth is the largest sample value collected between the last polling interval (or server startup) and the Lookup time. See the description of Average Bandwidth Usage, earlier in this section, for more information about polling. |
| Minimum Dequeue Bandwidth Usage | The minimum bandwidth used by the selected device to dequeue SharePoint Workspace data on the Relay server since the last poll. Minimum bandwidth is the smallest sample value collected between the last polling interval (or server startup) and the Lookup time. See the description of Average Bandwidth Usage, earlier in this section, for more information about polling. |
| Detailed Dequeue Bandwidth Usage (Bytes/Sec) Since Last Poll: | |
| Identity | A SharePoint Workspace identity that dequeued on the Relay server since the last poll. Dequeuing statistics appear for each identity dequeuing from the selected device since the last poll. Note that, following Groove’s SSTP protocol, separate identity information is provided for dequeuing only, not for enqueuing. |
| Average Dequeue Bandwidth Usage | The average bandwidth used by an identity dequeuing on the Relay server from the selected device since the last poll. |
| Maximum Dequeue Bandwidth Usage | The maximum bandwidth used by an identity dequeuing on the Relay server from the selected device since the last poll. |
| Minimum Dequeue Bandwidth Usage | The minimum bandwidth used by an identity dequeuing on the Relay server from the selected device since the last poll. |
SharePoint Workspace client devices
The Devices link on the Relay server administrative Web page displays the current list of SharePoint Workspace devices that have contacted the Relay server. From this devices list page, you can click a device or enter a device name in the Lookup text box to view detailed information about a specific device, as described in the following table:
| Device information | Description |
|---|---|
| Device Information: | |
| URL | The globally unique URL of the device. |
| LastProductVersion | The device version reported at the time of connection to the Relay server. |
| LastProductCapabilities | Reserved field. |
| SuccessfulConnects | The number of times the device has successfully connected to the Relay server, since the device’s initial registration with the Relay server. |
| LastSuccessfulConnect | The date and time that the device last successfully connected to the Relay server. |
| FailedConnects | The number of times that the device did not successfully connect to the Relay server, since the device’s initial registration with the Relay server. |
| LastFailedConnect | The date and time that the device last did not connect to the Relay server. |
| LastFailureReason | The reason for the device’s last failure to connect to the Relay server. |
| LastApparentIP | The IP address associated with the device’s last successful connection to the Relay server. |
| LastClientPort | The port number that was used by the device for its last successful connection to the Relay server. |
| ClientIPAdrs | A list of the device’s local IP addresses that are included in the DPP publish information. |
| Accounts for this device | The number of SharePoint Workspace client accounts defined on this device. |
| Device targeted queues | The number of device-targeted messages (Groove deltas, updates to workspaces, contacts, or tools) queued for this device. |
| Header Information | The version, date created, update information, and size in bytes of the current record. |
| Device Index button | Displays Device Index Entry pages together with current Device Presence Protocol (DPP) information about the client device, including the following: Device data, including the device’s IP address and Groove state (online or offline) Subscribers, including the device’s client message queues and account information. Subscribers are those SharePoint Workspace clients that are contacting the Relay server for presence information about another client. |
SharePoint Workspace device index
The Device Index link on the Relay server administrative Web page displays the current list of SharePoint Workspace devices that are connected to the Relay server or that are subscribed to by another client device. From this devices list page, you can click a device or enter a device name in the Lookup text box to view detailed information about a specific device, as described in the following table:
| Connected device information | Description |
|---|---|
| General Device Information: | |
| Online Mode | Yes or No to indicate whether a SharePoint Workspace device is online. |
| NumSubscribers | The number of SharePoint Workspace devices subscribing to the Relay server for a particular client’s presence information. For example, if a device on this page has a value of 4 in this column, that SharePoint Workspace client appears in the SharePoint Workspace contact lists of at least four other SharePoint Workspace users who are currently online. Note that this value is a minimum. |
| IPAddrs | The number of IP addresses associated with each device. |
| Owner | Reserved field. |
| Attaches | Indicates a device has been successfully authenticated by the Relay server. |
| Version | The SharePoint Workspace version being run on each device. |
| Individual Device Information | |
| Device Data: | |
| RealIP | The real IP address of this device. |
| ClientSSTPPort | The SSTP port name of this client device. |
| TranslatedIP | The external or proxy IP address of this device. |
| Translated Port | The external or proxy port name of this device. |
| Flags | Reserved field. |
| Version | The Relay server version being run on this device. |
| Device State | Online or offline. |
| Subscription Count | The number of subscribers to this device. |
| Subscribers | A list of SharePoint Workspace client devices that are subscribing to this Relay server for presence information about the selected client device. |
| Device Queues: | |
| Queuename | The Relay server name for the queue associated with this device connection. |
| Valid | Yes or No to indicate whether the queue name was parsed correctly. |
| Identity | The SharePoint Workspace identity URL associated with this queue. |
| Resource | The URL of this queue. |
| Device | The DPP URL associated with the selected device. Together, the Identity, Resource, and Device URLS uniquely identify the queue. |
| Attached Accounts | The URL of an authenticated account (if the device has attached to the Relay server). |
| Identity Registrations | The URL of authenticated identity associated with the device (if the device has attached to the Relay server). |
SharePoint Workspace user identities
The Identities link on the Relay server administrative Web page displays the current list of SharePoint Workspace identities that have contacted the Relay server. From this identities list page, you can click an identity or enter an identity name in the Lookup text box to view detailed information about a specific identity, as described in the following table:
| Identity information | Description |
|---|---|
| Identity Information: | |
| URL | The globally unique URL of the user identity URL. |
| Name | The GUID piece of the user identity. |
| Account Name | The name of the account associated with this identity. |
| Identity targeted queues | The number of identity-targeted messages (instant messages and workspace invitations) queued for this identity. |
| Header Information | The version, date created, update information, and size in bytes of the current record. |
Relay server queues
The Queues link on the Relay server administrative Web pages displays the current list of Relay server queues. From this queue list page, you can click a queue or enter a queue name in the Lookup text box to view detailed information about a specific queue, as described in the following table. You can also click the Purge button to purge a specific queue, as described in Managing Groove Server Relay databases.
| Queue information | Description |
|---|---|
| Header Information | The version, date created, update information, and size in bytes of the current record. |
| Queue Details: | |
| Name | The globally unique URL of the queue. |
| Identity URL | The globally unique URL of the identity associated with the queue. |
| Device URL | The globally unique URL of the device associated with the queue. |
| Resource URL | The globally unique resource URL for this queue. |
| Store Name | The name of the associated queue store. |
| Queued | The number of bytes queued, followed by the number of messages queued. |
| Store Details - Common Store Information: | |
| LastPurge Time | The date and time that the queue was last purged from the Relay server or by clicking the Purge all queues button on the Maintenance page of the Relay server statistics. For information about database purges, see Relay server database purges. |
| FFQ Store Information: This information is for use by Microsoft Support. | |
| Purge button | Purges the queue. |
Relay server queue stores
The Stores link on the Relay server administrative Web pages displays a subset of information that is provided in the Queues pages, described in Relay server queues. Stores organize queue data into specific volumes. Currently, only one volume is used for queue stores.
Relay server users
The Users link on the Relay server administrative Web pages displays the identifiers and URLs of SharePoint Workspace users that are connected to the Relay server. Click a user identifier to view the account number and Relay server lockout status. Click the user account URL to display the account information, described in SharePoint Workspace client accounts.
Relay server connections
The Relay Connections link on the Relay server administrative Web pages displays information about other Relay servers with which the reporting Relay server communicates. Click a foreign Relay server connection to view connection information, as described in the following table
| Foreign Relay server connection information | Description |
|---|---|
Relay server name |
Name of the foreign Relay server. |
Status |
Connection status: Connected to indicate successful connectivity, or an error code to indicate failure. |
Sessions |
Number of sessions that are open between each foreign Relay server and the reporting Relay server. |
Time of most recent connection attempt |
The time of the most recent connection attempt between each remote Relay server and the reporting Relay server. |
Relay server trace logs
The Trace Log link, on the Relay server administrative Web pages, displays a subset of the Relay server’s internal trace information, reported in the Data\Diagnostics directory. This information is useful primarily to Microsoft Support.
Relay server Event Log
The Event Log link on the Relay server administrative Web pages displays the most recent Relay server events reported to the Windows Event Log. Event Log entries can be helpful in diagnosing server problems.
You can access the Windows Event Log service by using the Event Viewer, as described in Monitoring Groove Server Relay. You can create and query Event Logs and associate programs with particular logged events, by using command-line utilities, including the following:
Eventcreate.exe to create customized Event Logs.
Eventquery.vbs to list the events and event properties from one or more Event Logs.
Eventtriggers.exe to create event triggers that will run programs upon the occurrence of specific Event Log events.
For information about other command-line utilities, see the Windows Command-Line Reference.
The Relay server generates the following categories of events:
Critical events, codes 100-6999 (including server state changes, service state changes, process dumps, call-stack dumps)
Administrative events, codes 7000-7999 (including queue report status, purge status, database metadata save)
Resource monitoring events, codes 8000-8999 (including resource exhaustion, free disk space limits, protocol connection limits approached)
Event messages may be one of the following types:
Error (automatic action may be taken by the Relay server, such as shutting down; or manual intervention may be required by the administrator, such as purging Relay queues or other disk cleaning measure)
Warning (action may be required to prevent an error condition)
Informational (no action required)
You can view Relay server events together with system and other events by using the Windows Event Viewer.
Relay server database purges
The Maintenance link on the Relay server administrative Web pages enables Relay server administrators to purge database queues on the Relay server and view the status of any manual or scheduled purge. This page lets you start and view queue purges.
The Purge all queues to the configured purge interval link lets you purge all queues of messages older than the designated message lifetime, as described in Managing Groove Server Relay databases. For information about how to set message lifetime, use the associated Groove Server Manager to configure the Relay server purge settings, as described in Registering Relay servers with Groove Server Manager.
The Purge status link lets you view the status for any purge event, automatic or manual. Purge status displays the following information:
Number of queue stores purged
Number of purged messages
Number of bytes purged
Number of bytes compressed
Every time that the Relay server purges queues, it writes a purge report to the Groove Relay Data\Diagnostics\PurgeInfo directory. The report file name is PurgeInfo-yy-mm-dd-hhmmss.log (where yy-mm-dd-hhmmss represents the year-month-day-hours, minutes, seconds). The purge report displays two lines of information per queue. This information includes the number of messages and bytes used in the queue before the purge, and the number of message and bytes used in the queue after the purge.
Note that purge information is also reported in the Windows Event Log.
For more information about how to purge Relay server database queues and for other information about database queues, see Managing Groove Server Relay databases.
Relay server queue reports
The Maintenance link on the Relay server administrative Web pages enables Relay server administrators to generate a Relay server queue information report in the Diagnostics/Info subdirectory of the Relay server Data\Diagnostics directory. The resulting log files display data on each queue which can then be imported into a spreadsheet (such as Microsoft Excel) or database application (such as Microsoft Access). The report file name is QueueInfo-yy-mm-dd-hhmmss.log file (where yy-mm-dd-hhmmss represents the year-month-day-hours, minutes, seconds)
To generate a Relay server queue report, click the Maintenance link, and then the Generate Queue Information Report link. The report displays the information described in the following table:
| Queue information report fields | Descriptions |
|---|---|
Current date and time |
The date and time of report generation. |
Identity URL |
The globally unique identity URL for this queue. |
Device URL |
The globally unique device URL for this queue, if the queue is device-targeted. A null value indicates an identity-targeted queue. |
Resource URL |
The workspace URL for this queue. |
Date/Time that queue was created (mm/dd/yy hh/mm/ss) |
The date and time that this queue was created. |
LastAppend |
The date and time when a SharePoint Workspace message was last written to this queue. |
LastGetNext |
The date and time when a SharePoint Workspace message was last read from this queue. |
LastAdvance |
The date and time when a SharePoint Workspace message was last removed from this queue because message receipt was acknowledged by the client. |
Refresh Relay server configuration values
To refresh Groove Server Relay configuration values to those that are stored in the Windows registry, click the Refresh Relay configuration values from configuration registry. Only some values can be updated while the Relay server is running. For example, most string values are not refreshable.
Warning
Avoid refreshing Relay server configuration values while the Relay server is running. If there are dependencies between multiple values during a configuration update while the Relay server is running, Relay server behavior is unpredictable.