Lync Server 2013 的最大失敗報告Top Failures Report in Lync Server 2013

 

主題上次修改日期: 2012-10-01Topic Last Modified: 2012-10-01

Top Failures 報告列出最常發生的失敗及其在一段時間後的趨勢。The Top Failures Report provides a look at the most-commonly reported failures and their trends over time. Failures are based on a combination of the following two metrics:

  • 診斷 ID。附加在 SIP 訊息中的唯一識別碼 (採用 ms-diagnostics 標頭的格式)。診斷 ID 可以在疑難排解通話相關錯誤時提供實用的資訊。Diagnostic ID. Unique identifier (in the form of an ms-diagnostics header) that is attached to a SIP message. Diagnostic IDs provide information useful in troubleshooting call-related problems.

  • 回應碼Response code. 回應碼用於 SIP 通訊會話中,以回應 SIP 要求。Response codes are used in SIP communication sessions to respond to SIP requests. 例如,當 Ken 將 INVITE 要求傳送給 Pilar Ackerman (也就是說,假設 Ken Myer 呼叫 Pilar Ackerman) 。For example, suppose Ken sends the INVITE request to Pilar Ackerman (that is, suppose Ken Myer calls Pilar Ackerman). 如果 Pilar 答案,她的電話會傳送回應碼 200 (確定) ,讓 Ken 電話知道 Pilar 已應答。If Pilar answers, her phone will send the response code 200 (OK), letting Ken's phone know that Pilar has answered. 最上層失敗報告只包含回應通話失敗時傳送的回應碼。Lync Server 不會追蹤通話期間發出的所有回應碼。The Top Failures Report only includes response codes that were sent in response to a call failure; Lync Server does not keep track of all the response codes issued during the course of a call.

資訊回報內容不僅有發生失敗的工作階段總數,還有因失敗受到影響的使用者總數。Information is reported not only for the total number of sessions where a failure occurred but also for the total number of users who were impacted by the failure.

存取最大失敗報告Accessing the Top Failures Report

可以從監視報告首頁存取最大失敗報告。The Top Failures Report is accessed from the Monitoring Reports home page. 按一下已報告的會話度量將會帶您前往 Lync Server 2013 的失敗散佈報告Clicking the Reported sessions metric will take you to the Failure Distribution Report in Lync Server 2013.

善用最大失敗報告Making the Best Use of the Top Failures Report

在某方面而言,最大失敗報告顯得十分特別:此報告最多能讓您一次篩選 5 個診斷 ID (通常一次只能篩選一個項目,例如一個使用者 SIP 位址)。若要篩選多個診斷 ID,只要在「診斷 ID」方塊中輸入各個 ID,並以逗號區隔即可 (也可以在每個逗號後面留下空格)。例如:The Top Failures Report is unusual in one regard: it allows you to filter on as many as 5 diagnostic IDs at once. (Typically you can only filter on one item – such as one user SIP address – at a time.) To filter on multiple diagnostic IDs, simply enter each ID in the Diagnostic IDs box, separating the IDs by using commas. (If you want to, you can leave a blank space after each comma.) For example:

1011, 2412, 1033, 52116, 10081011, 2412, 1033, 52116, 1008

完成後,只會顯示回報五個診斷 ID 中至少有一個 ID 的失敗通話。Do that, and only failed calls that reported at least one of those five diagnostic IDs will be displayed.

如果您將滑鼠移到回應碼時會看到工具提示,說明有問題的回應代碼所代表的涵義。例如將滑鼠移到回應碼 486,會看到此訊息:If you hold your mouse over a Response code you'll see a tooltip that tells you what the Response code in question means. For example, if you hold the mouse over the Response code 486 you'll see this message:

此處非常忙碌。Busy Here.

篩選Filters

篩選器可以讓您傳回更精確的資料集或者以不同方法檢視傳回的資料。例如,「最大失敗報告」可讓您依據活動類型之類的項目 (對等工作階段或會議工作階段),或是依失敗工作階段隨附的 SIP 回應碼,篩選傳回的資料。您也可以選擇資料的分組方式。在這種情況下,使用量會按照小時、日、星期或月加以分組。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 Top Failures Report enables you to filter the returned data based on such things as the activity type (peer-to-peer session or conferencing session) or by the SIP response code that accompanied the failed session. You can also choose how data should be grouped. In this case, usages are grouped by hour, day, week, or month.

下表列出您可以用於最大失敗報告的篩選器。The following table lists the filters that you can use with the Top Failures Report.

最大失敗報告篩選器Top Failures Report Filters

名稱Name 描述Description

FromFrom

時間範圍的開始日期/時間。若要按照小時檢視資料,請輸入開始日期和時間,如下所示:Start date/time for the time range. To view data by hours, enter both the start date and time as follows:

7/7/2012 1:00 PM7/7/2012 1:00 PM

如果您未輸入開始時間,報告會自動從指定日期凌晨 12 點開始。若要按照日期檢視資料,只要輸入日期即可: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:

7/7/20127/7/2012

若要按星期或月份檢視,請輸入當週或該月您想檢視的日期 (您不必輸入當週或該月的第一天):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):

7/3/20127/3/2012

星期永遠是從星期日開始星期六結束。Weeks always run from Sunday through Saturday.

ToTo

時間範圍的結束日期/時間。若要按照小時檢視資料,請輸入開始日期和時間,如下所示:End date/time for the time range. To view data by hours, enter both the end date and time as follows:

7/7/2012 1:00 PM7/7/2012 1:00 PM

如果您未輸入結束時間,報告會自動在指定日期凌晨 12 點結束。若要按照日期檢視資料,只要輸入日期即可: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:

7/7/20127/7/2012

若要按星期或月份檢視,請輸入當週或該月您想檢視的日期 (您不必輸入當週或該月的第一天):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):

7/3/20127/3/2012

星期永遠是從星期日開始星期六結束。Weeks always run from Sunday through Saturday.

活動類型Activity type

活動的類型。請選取下列其中一項:Type of activity. Select one of the following:

  • 一切[All]

  • 對等Peer-to-peer

  • 會議Conference

形態Modality

目前唯一可用的選項是 [全部]At this time the only option available is [All].

集區Pool

登錄器集區或 Edge Server 的完整網域名稱 (FQDN)。您可以選取個別的集區,或是按一下 [全部] 檢視所有集區的資料。此下拉式清單會自動將資料庫內的資料填入。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.

類別Category

遇到的失敗類型。請選取下列其中一項:Type of failure experienced. Select one of the following:

  • 預期及未預期的失敗Both expected and unexpected failure

  • 未預期的失敗Unexpected failure

"預期的失敗 " 是預期會發生的失敗。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. 未 " 預期的失敗 " 是指出現在其他狀況良好之系統上的失敗。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.

回應碼Response code

會議失敗時所傳送的 SIP 回應碼。請輸入完整的回應碼,例如:SIP response code sent when the conference failed. Enter the entire response code For example:

400400

診斷識別碼Diagnostic ID

附加在 SIP 訊息中的唯一識別碼 (採用 ms-diagnostics 標頭的格式),常可以在疑難排解錯誤時提供實用的資訊。診斷標頭為選用 (也可能有 SIP 工作階段不包含這些標頭)。只有發生特定問題的工作階段才會回報診斷識別碼。Unique identifier (in the form of an ms-diagnostics header) attached to a SIP message that often provides information useful in troubleshooting errors. Diagnostics headers are optional (it is possible to have SIP sessions that do not include these headers), and diagnostic IDs are reported only for sessions that experienced problems of some kind.

指標Metrics

下表列出前幾名失敗報告提供的資訊。The following table lists the information provided in the Top Failures Report.

最大失敗報告計量Top Failures Report Metrics

姓名Name 可以排序這個項目嗎?Can you sort on this item? 描述Description

RankRank

Yes

依據所報告之工作階段數的相對排名。Relative rank based on the number of reported sessions.

報告的工作階段Reported sessions

Yes

依據診斷識別碼及 SIP 回應碼的失敗工作階段總數。Total number of failed sessions based on diagnostic ID and SIP response code.

受影響的使用者Users impacted

Yes

受失敗工作階段影響的使用者總數。Total number of users affected by the failed session.

失敗資訊Failure information

No

失敗的詳細資訊,包括診斷識別碼、SIP 回應碼,以及工作階段為什麼失敗的說明。Detailed information about the failure, including diagnostic ID, SIP response code, and description of why the session failed.

過去的趨勢Trend in the past

No

一段時間的失敗工作階段圖表。Graphs failed sessions over time.