运行状况报告Health report

" 合作伙伴中心" 中的 运行状况 报告使你可以获取与应用的性能和质量相关的数据,包括故障和无响应事件。The Health report in Partner Center lets you get data related to the performance and quality of your app, including crashes and unresponsive events. 您可以在 "合作伙伴中心" 中查看此数据,或 下载该报表 以脱机查看。You can view this data in Partner Center, or download the report to view offline. 如果适用,可以查看堆栈跟踪和/或 CAB 文件以便进一步调试。Where applicable, you can view stack traces and/or CAB files for further debugging.

或者,也可以使用 Microsoft Store 分析 REST API 以编程方式检索数据。Alternatively, you can programmatically retrieve the data in this report by using the Microsoft Store analytics REST API.

应用筛选器Apply filters

在页面顶部附近,可以选择希望显示数据的时间段。Near the top of the page, you can select the time period for which you want to show data. 默认选择是 72H (72 小时),但可以改选 30D 以显示最近 30 天的数据。The default selection is 72H (72 hours), but you can choose 30D instead to show data over the last 30 days. 请注意,数据在 72H 视图的本地时区中显示,对于 30D 视图为 UTC。Note that data is shown in your local time zone for the 72H view and in UTC for the 30D view.

还可以展开 筛选器 ,以按照程序包类型、市场和/或设备类型筛选该页面上的所有数据。You can also expand Filters to filter all of the data on this page by package version, market, and/or device type.

  • 程序包版本 :默认设置为 全部Package version : The default setting is All . 如果应用包含多个程序包,可以在此处选择一个特定程序包。If your app includes more than one package, you can choose a specific one here.
  • 市场 :默认筛选器是 所有市场 ,但可以将数据限制为一个或多个市场。Market : The default filter is All markets , but you can limit the data to one or more markets.
  • 设备类型 :默认设置为 全部 ,但可以选择仅为一种特定设备类型显示数据。Device type : The default setting is All , but you can choose to show data for only one specific device type. 请注意, 其他 类别包括制造商/型号被识别,但无法将其加入此筛选器中显示的其中一个预定义类别的设备。Note that the Other category includes devices where the make/model is recognized but we aren't able to include it into one of the pre-defined categories shown in this filter. 对于这些设备,可以在 故障详细信息 报告的 故障日志 部分查看设备型号。For these devices, the device model can be viewed in the Failure log section of the Failure details report.
  • 操作系统版本 :默认值是 所有操作系统版本 ,但你可以选择特定的操作系统版本。OS version : The default is All OS versions , but you can choose a specific OS version.
  • 操作系统发行版本 :默认设置为 所有操作系统发行版本 ,但可以选择所选 操作系统版本 的特定发行版本。OS release version : The default is All OS release versions , but you can choose a specific release version of the selected OS version .
  • 沙盒 :默认为 零售 ,但对于使用多个开发沙盒的产品(如与 Xbox Live 集成的游戏),你可以在此处选择特定沙盒。Sandbox : The default is Retail , but for products that use multiple development sandboxes (such as games which integrate with Xbox Live), you can choose a specific one here. (如果你的产品不使用沙盒,此筛选器将仅显示 零售 且不适用。)(If your product doesn't use sandboxes, this filter will show only Retail and won't be applicable.)
  • 体系结构 :默认设置为 所有体系结构 ,但可以选择特定的系统体系结构类型。Architecture : The default is All architectures , but you can choose a specific system architecture type. 仅当选择 30D 时此筛选器才可用。This filter is only available when 30D is selected.
  • PRAID :默认设置为 所有 ,但如果在创建应用包时,你定义了多个包相对应用 ID (PRAID),你可以选择只显示与一个 PRAID 相关的数据。PRAID : The default setting is All , but if you defined multiple package relative app IDs (PRAIDs) when creating your app package, you can choose to show only data related to one PRAID. 如果你未定义多个 PRAID,将不会显示此筛选器。This filter will not appear if you have not defined multiple PRAIDs.

下面列出的所有图表中的信息将反映所选的日期范围和任何筛选器。The info in all of the charts listed below will reflect the date range and any filters you've selected. 某些部分还允许应用其他筛选器。Some sections also allow you to apply additional filters.

故障发生Failure hits

故障发生 图显示在所选时段内,客户在使用应用时每日遇到的崩溃和事件数量。The Failure hits chart shows the number of daily crashes and events that customers experienced when using your app during the selected period of time. 应用所遇到的每种事件将受到单独跟踪:崩溃、挂起、JavaScript 异常和内存故障。Each type of event that your app experienced is tracked separately: crashes, hangs, JavaScript exceptions, and memory failures.

选择 30D 时间段时,可能会看到圆形标记。When the 30D time period is selected, you may see circle markers. 这表示我们想要了解的给定值中的显著增加或减少。These represent a significant increase or decrease in a given value that we think you'll want to know about. 圆圈的显示日期表示一周的结束时间,与此之前的周相比,这一周结束。The date on which the circle appears represents the end of the week in which we detected a significant increase or decrease compared to the week before that. 若要查看有关更改内容的更多详细信息,请将鼠标悬停在该圆圈上。To see more details about what's changed, hover over the circle.

提示

您可以查看更多与 insights 报告中过去30天内的重大更改相关的见解。You can view more insights related to significant changes over the last 30 days in the Insights report.

按市场的故障发生Failure hits by market

按市场的故障发生 图按市场显示所选时段内的崩溃和事件总数。The Failure hits by market chart shows the total number of crashes and events over the selected period of time by market.

可以在可视 地图 窗体中查看此数据,或切换设置以在 表格 窗体中查看。You can view this data in a visual Map form, or toggle the setting to view it in Table form. “表格”窗体一次显示五个市场,并且按字母顺序或用户会话最大/最小次数排序。Table form will show five markets at a time, sorted either alphabetically or by highest/lowest number of user sessions. 还可以下载数据,以便一起查看所有市场的信息。You can also download the data to view info for all markets together.

包版本Package version

包版本 图表按包版本显示所选时间段内的崩溃和事件总数。The Package version chart shows the total number of crashes and events over the selected period of time by package version. 默认情况下,我们按发生数从高到低的顺序显示程序包版本。By default, we show you the package version that had the most hits on top and continue downward from there. 可以通过切换此图的“发生” 列中的箭头颠倒此顺序。You can reverse this order by toggling the arrow in the Hits column of this chart.

失败数Failures

" 失败 " 图表按故障名称显示所选时间段内的崩溃和事件总数。The Failures chart shows the total number of crashes and events over the selected period of time by failure name. 每个故障名称由四个部分组成:一个或多个问题类、异常/错误检查代码、发生故障的图像/驱动程序的名称和相关的函数名称。Each failure name is made up of four parts: one or more problem classes, an exception/bug check code, the name of the image/driver where the failure occurred, and the associated function name. 默认情况下,我们按发生数从高到低的顺序显示故障。By default, we show you the failure that had the most hits on top and continue downward from there. 可以通过切换此图的“发生” 列中的箭头颠倒此顺序。You can reverse this order by toggling the arrow in the Hits column of this chart. 对于每个故障,还会显示其所占故障总数的百分比。For each failure, we also show its percentage of the total number of failures.

提示

有时,你可能会在此部分看到 未知 的条目。At times, you may see an entry for Unknown in this section. 尽管我们尽最大努力也会发生此情况,我们无法收集一个或多个故障的完整详细信息,它们将全部被分组在 未知 下。This occurs when despite our best efforts, we are unable to collect full details for one or more failures, which will all be grouped together under Unknown . 多数情况下,发生这种情况是由于存储限制,但也可能是由于设备的隐私设置、网络连接问题、部分/失败故障转储以及其他因素。Most often, this occurs because of storage constraints, but it can also be a result of a device's privacy settings, network connection issues, partial/bad crash dumps, and other factors.

如果你在故障名称中看到有 !unknown ,这意味着符号不存在,因此我们无法识别故障名称。If you see !unknown as part of a failure name, this means that symbols weren’t present, so we couldn’t identify the failure name. 请务必在程序包中加入符号以获取准确的故障分析。Be sure to include symbols in your package to get accurate failure analysis. 请参阅配置应用包See Configure an app package. 相反,包含 !unknown_error_in_!unknown_function 的故障名称则意味着我们由于各种其他原因无法收集完整的详细信息。In contrast, failure names that include !unknown_error_in_ and !unknown_function mean that we weren’t able to gather complete details for various other reasons.

若要显示特定失败的 失败详细信息 报告,请选择 "失败" 名称。To display the Failure details report for a particular failure, select the failure name. 如果包含了符号文件, 故障详细信息 报告将包括过去一个月的故障发生数、列出发生详细信息(日期、程序包版本、设备类型、设备型号、操作系统版本)的故障日志以及指向堆栈跟踪和/或 CAB 文件的链接(如可用)。If you have included symbol files, the Failure details report includes the number of failure hits over the last month, as well as a failure log that lists occurrence details (date, package version, device type, device model, OS build) and a link to the stack trace and/or CAB file, if available.

提示

仅当故障发生在使用 Windows 预览体验成员版本的计算机中时 CAB 文件才将可用,因此并非所有故障都将包含 CAB 下载选项。CAB files will only be available when the failure occurred on a computer using a Windows Insider build, so not all failures will include the CAB download option. 若要仅显示具有 CAB 文件的故障,请在 "筛选器" 部分中选择 " 下载失败 "。To show only failures that have CAB files, select Failures with downloads in the section filter. 还可以单击 失败日志 中的 链接 标头对结果进行排序,以便将包含 CAB 文件的故障显示在列表的顶部。You can also click the Links header in the Failure log to sort the results so that failures which include CAB files appear at the top of the list.

在 " 失败详细信息 " 页上,你还将看到 " 堆栈堆积 " 图表,其中显示了导致故障的顶层堆栈,按百分比排序,而 设备配置 (30D) 图表,提供有关发生故障的设备的配置的详细信息。On the Failure details page, you'll also see the Stack prevalence chart, which shows the top stacks that contributed to the failure, ordered by percentage, and the Device configuration (30D) chart, which provides details about the configuration of devices which experienced the failure.

无崩溃会话和设备 (30D) Crash-free sessions and devices (30D)

" 无故障会话和设备 " 图表显示过去30天内未出现故障的设备或用户会话的百分比。The Crash-free sessions and devices chart shows the percent of devices or user sessions that did not experience a crash in the past 30 days. 此信息可帮助你了解崩溃对用户造成的影响。This info helps you understand how broadly your crashes are affecting your users. 例如,应用可能在一天内发生了10000故障。For example, an app could have 10,000 crashes in one day. 如果90% 的设备受到影响,则可能会将该设备分类为重要,并立即对其进行修复。If 90% of your devices are affected, then you would probably classify that as critical and act to fix it right away. 但是,如果仅使用你的应用代表5% 的设备,则优先级可能较低。However, if that only represents 5% of devices using your app, the priority might be lower.

此图表有两个选项卡:This chart has two tabs:

  • 无故障设备 :显示在过去30天内 (每日出现故障的唯一设备的百分比) 。Crash-free devices : Shows the percentage of unique devices that did not experience a failure on each day (during the past 30 days).
  • 无故障会话 :显示在过去30天内 (每日出现故障的唯一用户会话的百分比) 。Crash-free sessions : Shows the percentage of unique user sessions that did not experience a failure on each day (during the past 30 days).