Measures reported by SPOSiteHealthCheckTest
SharePoint Online includes a set of rules that you can run against a site collection to verify that it is working as expected. These rules are part of the site collection health checks.
You run the health checks manually to prepare for an upgrade. In addition, the health checks are run automatically in repair mode when you start to upgrade a site collection.
The site collection health checker includes the following rules:
| Rule Name |
Description |
| Conflicting Content Types |
This rule checks for conflicts between existing content types and content types that are created when you upgrade the site. A conflict occurs when both content types have the same name. |
| Customized Files |
This rule checks for any files that were customized (or unghosted) in the site collection or subsites. When run in repair mode, it can reset the page to the default (reghost the file). |
| Missing Galleries |
This rule checks for all default galleries and reports if any are missing from the site collection or subsites. |
| Missing Parent Content Types |
This rule checks for missing parent content types. If a missing parent content type is found, you can either delete the orphaned content type or associate the orphaned content type with a different parent content type. |
| Missing Site Templates |
This rule checks to make sure that the template the site is based on is available and reports if any elements are missing. |
| Unsupported Language Pack References |
This rule checks to make sure that the language packs that are used by the site collection exist and are referenced correctly by the site collection. |
| Unsupported MUI References |
This rule checks to make sure that the multi-user interface elements that are used by the site collection exist and are referenced correctly. |
Whenever one/more of the aforesaid health checks are run - whether manually or automatically - an administrator needs to know which health checks were run, on which site collection they were run, which of these checks passed, and which ones failed. This way, administrators can identify the unhealthy site collections or collections that are not upgrade-ready. Additionally, the knowledge of rules that failed will enable administrators initiate measures to investigate the reasons for the failure and fix them, so that they can then confidently proceed to upgrade the site collections. This is what the SPOSiteHealthCheckTest test helps administrators achieve!
This test automatically discovers the site collections on which health checks are run, and reports the count of rules that passed, rules that failed with warnings, and rules that failed with errors. This will point administrators to unhealthy site collections or site collections that are not upgrade-ready. Using the detailed diagnostics provided by the test, administrators can accurately identify the precise rules that passed and failed, and can thus easily troubleshoot the failures.
Outputs of the test : One set of results for each site collection.
First-level descriptor: Site collection URL
The measures made by this test are as follows:
| Measurement |
Description |
Measurement Unit |
Interpretation |
| Passed |
Indicates the number of health checks run on this site collection that passed. |
Number |
Use the detailed diagnosis of this measure to know which rules passed. |
| Failed_warnings |
Indicates the number of health checks run on this site collection that failed with warnings. |
Number |
Use the detailed diagnosis of this measure to know which rules failed with warnings. |
| Failed_errors |
Indicates the number of health checks run on this site collection that failed due to errors. |
Number |
Use the detailed diagnosis of this measure to know which rules failed owing to errors. |
|