Skip to content

Commit e5901f1

Browse files
committed
Add lightboxes
1 parent a121778 commit e5901f1

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/operator-nexus/troubleshoot-unhealthy-degraded-storage-appliance.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ You can see the current usage of the appliance by navigating to the Storage Appl
2424
navigating to the `Monitoring > Metrics` tab, and selecting `Nexus Storage Array Space Utilization` from
2525
the `Metric` dropdown.
2626

27-
:::image type="content" source="media/storage-metrics-utilization.png" alt-text="Screenshot of a metric showing the percentage utilization of a Storage Appliance.":::
27+
:::image type="content" source="media/storage-metrics-utilization.png" alt-text="Screenshot of a metric showing the percentage utilization of a Storage Appliance." ligthbox="media/storage-metrics-utilization.png":::
2828

2929
These issues can be addressed by reducing the load on the Storage Appliance. This outcome can be
3030
achieved by:
@@ -71,7 +71,7 @@ You can find more details of the specific alert(s), using the following instruct
7171
select all of the boxes. You will see a summary of the alert, and the vendor alert code. Use this information
7272
to search your vendor documentation for further details of the alert.
7373

74-
:::image type="content" source="media/storage-metrics-alerts.png" alt-text="Screenshot of a metric showing an active alert on a Storage Appliance.":::
74+
:::image type="content" source="media/storage-metrics-alerts.png" alt-text="Screenshot of a metric showing an active alert on a Storage Appliance." lightbox="media/storage-metrics-alerts.png":::
7575

7676
Once you have this information, use it to determine the appropriate next action. You should either:
7777

@@ -101,7 +101,7 @@ is the cause:
101101
- Click `+ New Chart`, and select the `Nexus Storage Array Performance Throughput Iops (Avg)` metric.
102102
Click `Apply Splitting`, and select `Dimension` as the dimension to split on.
103103

104-
:::image type="content" source="media/storage-metrics-latency-throughput.png" alt-text="Screenshot of a metric showing the latency and throughput on a Storage Appliance.":::
104+
:::image type="content" source="media/storage-metrics-latency-throughput.png" alt-text="Screenshot of a metric showing the latency and throughput on a Storage Appliance." lightbox="media/storage-metrics-latency-throughput.png":::
105105

106106
By comparing the resulting graphs, you can determine whether high load is the cause. If so, reduce the
107107
load to resolve the health event.
@@ -123,7 +123,7 @@ that starts shortly before the start time of the resource health alert. After id
123123
unhealthy network interface(s), and error types, you should raise a ticket with your Storage Appliance
124124
vendor.
125125

126-
:::image type="content" source="media/storage-metrics-network-errors.png" alt-text="Screenshot of a metric showing network interface errors on a Storage Appliance.":::
126+
:::image type="content" source="media/storage-metrics-network-errors.png" alt-text="Screenshot of a metric showing network interface errors on a Storage Appliance." lightbox="media/storage-metrics-network-errors.png":::
127127

128128
## Network latency
129129

0 commit comments

Comments
 (0)