diff --git a/windows/deployment/update/device-health-using.md b/windows/deployment/update/device-health-using.md index 3526ae3850..a7655bb672 100644 --- a/windows/deployment/update/device-health-using.md +++ b/windows/deployment/update/device-health-using.md @@ -90,7 +90,68 @@ Clicking a listed driver on the Driver-Induced OS Crashes blade opens a driver p The driver version table can help you determine whether deploying a newer version of the driver might help you reduce the crash rate. In the example shown above, the most commonly installed driver version (19.15.1.5) has a crash rate of about one-half of one percent--this is low, so this driver is probably fine. However, driver version 19.40.0.3 has a crash rate of almost 20%. If that driver had been widely deployed, updating it would substantially reduce the overal number of crashes in your organization. +## App Reliability +The App Reliability report shows you useful data on app usage and behavior so that you can identify apps that are misbehaving and then take steps to resolve the problem. + +### App reliability events + +The default view includes the **Devices with events** count, which shows the number of devices in your organization that have logged a reliability event for a given app over the last 14 days. A "reliability event" occurs when an app either exits unexpectedly or stops responding. + +![Main App Reliability view](images/app-reliability-main.png) + +When you click a particular app, the detailed **App reliability** view opens: + +![App reliability view with columns for app name, publisher, devices with usage, devices with events, percentage of devices with events logged for that app, and percentage of devices with events as a "commercial average"](images/app-reliability-app-detail.png) + +The view shows the following information for a given app: + +- App name +- Publisher +- Devices with usage: the number of unique devices that logged any usage of the app +- Devices with events: the number of unique devices that logged any reliability event for the app +- % with events: the ratio of "devices with events" to "devices with usage" +- % with events (commercial average): the ratio of "devices with events" to "devices with usage" in data collected from deployments with a mix of operating system versions and device models that is similar to yours. This can help you decide if a given app is having problems specifically in your environment or more generally in many environments. + +#### Trend view +[Click SOMETHING] to open the Trend view: + +![Trend view](images/app-reliability-trend-view.png) + +This view shows the 14-day trend in the reported reliability events, so you can more easily detect if the issue is growing, shrinking, or steady. The graph on the left the trend in number of devices that logged any reliability event for the app. The graph on the right shows the trend in the the ratio of "devices with events" to "devices with usage." + +Each graph displays two lines: + +- Trailing window: in this line, each day’s value reflects reliability events that occurred in the 14 days leading up to that day. This is useful for gauging the long-term trend with reduced volatility due to weekends and small populations. +- Single day: Each day’s value reflects reliability events that occurred in a single day. This is useful if an issue is quickly emerging (or being resolved). + +#### App and OS versions view +[Click SOMETHING] to open the App and OS versions view: + + +![App/OS version view](images/app-reliability-app-OS-version.png) + +This view is essentially the same as the detailed **App reliability** view, but with columns showing the versions of the app and Windows, to make it easier for you to identify patterns in either that might indicate the need to update or change configurations. + +For example, if the table shows that a later version is more reliable than an earlier version in your environment, then prioritizing deployment of the later version is likely the best path forward. However, if you are already running the latest version of the app, but reliability events are increasing, you might need to do some troubleshooting, or seek support from Microsoft or the app vendor. + +#### Reliability event history view + +[Click SOMETHING] to open the reliability event history view: + +![event history view](images/app-reliability-event-history.png) + +This table shows the most granular information available in the view. While Device Health is not a debugging tool, the details available in Reliability Event History are meant to boost troubleshooting efforts by providing the specific devices, versions, and dates of the crashes or hangs. +This table also contains the Diagnostic Signature column. When engaging support this value can be helpful in tying your situation to any known issues. The value is the same one (also known as Failure ID or Failure Name) used to summarize crash statistics for Microsoft and 3rd party developers. +The Diagnostic Signature value can also be helpful for troubleshooting on your own. It contains the type of reliability event, error code, DLL name, and function name. This information can drastically narrow the scope of troubleshooting. For example a value like APPLICATION_HANG_ThreadHang_Contoso-Add-In.dll!GetRegistryValue() implies that the app stopped responding when Contoso-Add-In was trying to read a registry value and got stuck. In this case you might prioritize updating/disabling the add-in, or using procmon to identify what registry value it was trying to read. This may lead to a resolution through antivirus exclusions, fixing missing keys, etc. + + + + + + + +## Login Health ## Windows Information Protection diff --git a/windows/deployment/update/images/app-reliability-app-OS-version.png b/windows/deployment/update/images/app-reliability-app-OS-version.png new file mode 100644 index 0000000000..c281dcc316 Binary files /dev/null and b/windows/deployment/update/images/app-reliability-app-OS-version.png differ diff --git a/windows/deployment/update/images/app-reliability-app-detail.png b/windows/deployment/update/images/app-reliability-app-detail.png new file mode 100644 index 0000000000..8c402bb91f Binary files /dev/null and b/windows/deployment/update/images/app-reliability-app-detail.png differ diff --git a/windows/deployment/update/images/app-reliability-event-history.png b/windows/deployment/update/images/app-reliability-event-history.png new file mode 100644 index 0000000000..f28ab02908 Binary files /dev/null and b/windows/deployment/update/images/app-reliability-event-history.png differ diff --git a/windows/deployment/update/images/app-reliability-main.png b/windows/deployment/update/images/app-reliability-main.png new file mode 100644 index 0000000000..18a1bd7f31 Binary files /dev/null and b/windows/deployment/update/images/app-reliability-main.png differ diff --git a/windows/deployment/update/images/app-reliability-trend-view.png b/windows/deployment/update/images/app-reliability-trend-view.png new file mode 100644 index 0000000000..2d26df93d3 Binary files /dev/null and b/windows/deployment/update/images/app-reliability-trend-view.png differ