You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: azure-local/manage/health-service-faults.md
+6-8Lines changed: 6 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -63,7 +63,7 @@ This section shows how to connect to the Health Service, use discover objects, a
63
63
64
64
### Connect
65
65
66
-
In order to query the Health Service, you establish a **CimSession** with the cluster. To do so, you will need some things that are only available in full Microsoft .NET, meaning you cannot readily do this directly from a web or mobile app. The code samples in this section use C\#, the most straightforward choice for this data access layer.
66
+
In order to query the Health Service, you establish a **CimSession** with the cluster. To do so, you will need some things that are only available in full Microsoft .NET, meaning you can't readily do this directly from a web or mobile app. The code samples in this section use C\#, the most straightforward choice for this data access layer.
67
67
68
68
```
69
69
using System.Security;
@@ -309,22 +309,20 @@ Note the **ChangeType** that indicates whether a fault is being created, removed
The Health Service in Azure Local and Windows Server can detect faults accross various system components, including storage, networking, and compute resources.
316
+
The Health Service in Azure Local and Windows Server can detect faults across various system components, including storage, networking, and compute resources.
318
317
319
318
For a detailed overview of health faults, including fault severity mappings, health settings (data types, fault associations, default values, and descriptions), and the list of collected metrics, download the [Health Service faults](https://github.com/Azure-Samples/AzureLocal/blob/main/health-service-faults/health-service-faults.xlsx) spreadsheet.
320
319
321
320
Considerations for Health Service faults:
322
321
323
322
- Some faults are disabled by default. To enable a fault, set the corresponding health setting to true.
324
-
325
-
For example, fault type `Microsoft.Health.FaultType.PhysicalDisk.HighLatency.AverageIO` is disabled by default. To enable it, set the health setting `System.Storage.PhysicalDisk.HighLatency.Threshold.Tail.Enabled` to true.
326
-
327
-
- The health of storage enclosure components, such as fans, power supplies, and sensors is derived from SCSI Enclosure Services (SES). If your vendor doesn't provide this information, the Health Service cannot display it.
323
+
- For example, fault type `Microsoft.Health.FaultType.PhysicalDisk.HighLatency.AverageIO` is disabled by default. To enable it, set the health setting `System.Storage.PhysicalDisk.HighLatency.Threshold.Tail.Enabled` to true.
324
+
- The health of storage enclosure components, such as fans, power supplies, and sensors are derived from SCSI Enclosure Services (SES). If your vendor doesn't provide this information, the Health Service cannot display it.
0 commit comments