Export (0) Print
Expand All

Peer-to-Peer Activity Diagnostic Report

 

Topic Last Modified: 2011-02-01

The Peer-to-Peer Activity Diagnostic Report provides an overall trend view of failed peer-to-peer sessions. A peer-to-peer session is one that involves just two participants.

Filters provide a way for you to return a more finely-targeted set of data or to view the returned data in different ways. For example, the Peer-to-Peer Activity Diagnostic Report enables you to filter on such things as the session modality (for example, instant messaging, file transfer, or application sharing). You can also choose how data should be grouped. In this case, calls are grouped by hour, day, week, or month.

The following table lists the filters that you can use with the Peer-to-Peer Activity Diagnostic Report.

Peer-to-Peer Activity Diagnostic Report Filters

Name Description

From

Start date/time for the time range. To view data by hours, enter both the start date and time as follows:

1/1/2011 1:00 PM

If you do not enter a start time, the report automatically begins at 12:00 AM on the specified day. To view data by day, enter just the date:

1/1/2011

To view by week or by month, enter a date that falls anywhere within the week or month that you want to view (you do not have to enter the first day of the week or month):

1/3/2011

Weeks always run from Sunday through Saturday.

To

End date/time for the time range. To view data by hours, enter both the end date and time as follows:

1/1/2011 1:00 PM

If you do not enter an end time, the report automatically ends at 12:00 AM on the specified day. To view data by day, enter just the date:

1/1/2011

To view by week or by month, enter a date that falls anywhere within the week or month that you want to view (you do not have to enter the first day of the week or month):

1/3/2011

Weeks always run from Sunday through Saturday.

Interval

Time interval. Select one of the following:

  • Hourly (a maximum of 25 hours can be displayed)

  • Daily (a maximum of 31 days can be displayed)

  • Weekly (a maximum of 12 weeks can be displayed)

  • Monthly (a maximum of 12 months can be displayed)

If the start and end dates exceed the maximum number of values allowed for the selected interval, only the maximum number of values (starting from the start date) is displayed. For example, if you select the Daily interval with a start date of 1/1/2011 and an end date of 2/28/2011, data is displayed for the days 8/1/2011 12:00 AM to 9/1/2011 12:00 AM (that is, a total of 31 days' worth of data).

Pool

Fully qualified domain name (FQDN) of the Registrar pool or Edge Server. You can either select an individual pool or click [All] to view data for all the pools. This drop-down list is automatically populated for you based on the records in the database.

Modality

Indicates the type of communication activity that took place. Select one of the following:

  • [All]

  • Instant messaging

  • File transfer

  • Application sharing

  • Audio

  • Video

The following table lists the information provided in the Peer-to-Peer Activity Diagnostic Report for each modality.

Metrics (per modality)

Name Can you sort on this item? Description

Success volume

No

Total number of successful peer-to-peer sessions.

Success percentage

No

Percentage of peer-to-peer sessions that completed with significant problems. Calculated by dividing the Success volume by the Total sessions.

Expected failure volume

No

Total number of sessions where an "expected failure" occurred.

An expected failure is a failure that is expected to happen. For example, if a user has set his or her status to Do Not Disturb you would expect any call to that user to fail.

Expected failure percentage

No

Percentage of peer-to-peer sessions that experienced an expected error. Calculated by dividing the Expected failure volume by the Total sessions.

Unexpected failure volume

No

Total number of sessions where an "unexpected failure" occurred.

An unexpected failure is a failure that occurs in what would appear to be an otherwise healthy system. For example, a call should not be terminated if the caller is placed on hold. If that occurs, that would be flagged as an unexpected failure.

Unexpected failure percentage

No

Percentage of peer-to-peer sessions that experienced an unexpected error. Calculated by dividing the Unexpected failure volume by the Total sessions.

Total sessions

No

Total number of sessions, including successful sessions, failed sessions (both expected failures and unexpected failures), and uncategorized sessions.

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft