Merge remote-tracking branch 'origin/main' into v23.2.19

src/current/v21.2/common-issues-to-monitor.md

@@ -257,10 +257,6 @@ Insufficient disk I/O can cause [poor SQL performance](#service-latency) and pot
 
 - The Linux tool `iostat` (part of `sysstat`) can be used to monitor IOPS. In the device status output, `avgqu-sz` corresponds to the **Disk Ops In Progress** metric. If service times persist in double digits on any node, this means that your storage device is saturated and is likely under-provisioned or misconfigured.
 
-{{site.data.alerts.callout_success}}
-Ensure that you [properly configure storage](#storage-and-disk-monitoring) to prevent I/O bottlenecks. Afterward, if service times consistently exceed 1-5 ms, you can add more devices or expand the cluster to reduce the disk latency.
-{{site.data.alerts.end}}
-
 With insufficient disk I/O, you may also see:
 
 - Degradation in [SQL response time](#service-latency).

src/current/v22.1/common-issues-to-monitor.md

@@ -261,10 +261,6 @@ Insufficient disk I/O can cause [poor SQL performance](#service-latency) and pot
 
 - The Linux tool `iostat` (part of `sysstat`) can be used to monitor IOPS. In the device status output, `avgqu-sz` corresponds to the **Disk Ops In Progress** metric. If service times persist in double digits on any node, this means that your storage device is saturated and is likely under-provisioned or misconfigured.
 
-{{site.data.alerts.callout_success}}
-Ensure that you [properly configure storage](#storage-and-disk-monitoring) to prevent I/O bottlenecks. Afterward, if service times consistently exceed 1-5 ms, you can add more devices or expand the cluster to reduce the disk latency.
-{{site.data.alerts.end}}
-
 With insufficient disk I/O, you may also see:
 
 - Degradation in [SQL response time](#service-latency).

src/current/v22.2/common-issues-to-monitor.md

@@ -287,10 +287,6 @@ Insufficient disk I/O can cause [poor SQL performance](#service-latency) and pot
 
 - The Linux tool `iostat` (part of `sysstat`) can be used to monitor IOPS. In the device status output, `avgqu-sz` corresponds to the **Disk Ops In Progress** metric. If service times persist in double digits on any node, this means that your storage device is saturated and is likely under-provisioned or misconfigured.
 
-{{site.data.alerts.callout_success}}
-Ensure that you [properly configure storage](#storage-and-disk-monitoring) to prevent I/O bottlenecks. Afterward, if service times consistently exceed 1-5 ms, you can add more devices or expand the cluster to reduce the disk latency.
-{{site.data.alerts.end}}
-
 With insufficient disk I/O, you may also see:
 
 - Degradation in [SQL response time](#service-latency).

src/current/v23.1/common-issues-to-monitor.md

@@ -293,10 +293,6 @@ Insufficient disk I/O can cause [poor SQL performance](#service-latency) and pot
 
 - The Linux tool `iostat` (part of `sysstat`) can be used to monitor IOPS. In the device status output, `avgqu-sz` corresponds to the **Disk Ops In Progress** metric. If service times persist in double digits on any node, this means that your storage device is saturated and is likely under-provisioned or misconfigured.
 
-{{site.data.alerts.callout_success}}
-Ensure that you [properly configure storage](#storage-and-disk-monitoring) to prevent I/O bottlenecks. Afterward, if service times consistently exceed 1-5 ms, you can add more devices or expand the cluster to reduce the disk latency.
-{{site.data.alerts.end}}
-
 With insufficient disk I/O, you may also see:
 
 - Degradation in [SQL response time](#service-latency).

src/current/v23.2/common-issues-to-monitor.md

@@ -297,10 +297,6 @@ Insufficient disk I/O can cause [poor SQL performance](#service-latency) and pot
 
 - The Linux tool `iostat` (part of `sysstat`) can be used to monitor IOPS. In the device status output, `avgqu-sz` corresponds to the **Disk Ops In Progress** metric. If service times persist in double digits on any node, this means that your storage device is saturated and is likely under-provisioned or misconfigured.
 
-{{site.data.alerts.callout_success}}
-Ensure that you [properly configure storage](#storage-and-disk-monitoring) to prevent I/O bottlenecks. Afterward, if service times consistently exceed 1-5 ms, you can add more devices or expand the cluster to reduce the disk latency.
-{{site.data.alerts.end}}
-
 With insufficient disk I/O, you may also see:
 
 - Degradation in [SQL response time](#service-latency).

src/current/v24.1/common-issues-to-monitor.md

@@ -297,10 +297,6 @@ Insufficient disk I/O can cause [poor SQL performance](#service-latency) and pot
 
 - The Linux tool `iostat` (part of `sysstat`) can be used to monitor IOPS. In the device status output, `avgqu-sz` corresponds to the **Disk Ops In Progress** metric. If service times persist in double digits on any node, this means that your storage device is saturated and is likely under-provisioned or misconfigured.
 
-{{site.data.alerts.callout_success}}
-Ensure that you [properly configure storage](#storage-and-disk-monitoring) to prevent I/O bottlenecks. Afterward, if service times consistently exceed 1-5 ms, you can add more devices or expand the cluster to reduce the disk latency.
-{{site.data.alerts.end}}
-
 With insufficient disk I/O, you may also see:
 
 - Degradation in [SQL response time](#service-latency).

src/current/v24.2/common-issues-to-monitor.md

@@ -297,10 +297,6 @@ Insufficient disk I/O can cause [poor SQL performance](#service-latency) and pot
 
 - The Linux tool `iostat` (part of `sysstat`) can be used to monitor IOPS. In the device status output, `avgqu-sz` corresponds to the **Disk Ops In Progress** metric. If service times persist in double digits on any node, this means that your storage device is saturated and is likely under-provisioned or misconfigured.
 
-{{site.data.alerts.callout_success}}
-Ensure that you [properly configure storage](#storage-and-disk-monitoring) to prevent I/O bottlenecks. Afterward, if service times consistently exceed 1-5 ms, you can add more devices or expand the cluster to reduce the disk latency.
-{{site.data.alerts.end}}
-
 With insufficient disk I/O, you may also see:
 
 - Degradation in [SQL response time](#service-latency).

src/current/v24.3/common-issues-to-monitor.md

@@ -297,10 +297,6 @@ Insufficient disk I/O can cause [poor SQL performance](#service-latency) and pot
 
 - The Linux tool `iostat` (part of `sysstat`) can be used to monitor IOPS. In the device status output, `avgqu-sz` corresponds to the **Disk Ops In Progress** metric. If service times persist in double digits on any node, this means that your storage device is saturated and is likely under-provisioned or misconfigured.
 
-{{site.data.alerts.callout_success}}
-Ensure that you [properly configure storage](#storage-and-disk-monitoring) to prevent I/O bottlenecks. Afterward, if service times consistently exceed 1-5 ms, you can add more devices or expand the cluster to reduce the disk latency.
-{{site.data.alerts.end}}
-
 With insufficient disk I/O, you may also see:
 
 - Degradation in [SQL response time](#service-latency).

src/current/v25.1/common-issues-to-monitor.md

@@ -297,10 +297,6 @@ Insufficient disk I/O can cause [poor SQL performance](#service-latency) and pot
 
 - The Linux tool `iostat` (part of `sysstat`) can be used to monitor IOPS. In the device status output, `avgqu-sz` corresponds to the **Disk Ops In Progress** metric. If service times persist in double digits on any node, this means that your storage device is saturated and is likely under-provisioned or misconfigured.
 
-{{site.data.alerts.callout_success}}
-Ensure that you [properly configure storage](#storage-and-disk-monitoring) to prevent I/O bottlenecks. Afterward, if service times consistently exceed 1-5 ms, you can add more devices or expand the cluster to reduce the disk latency.
-{{site.data.alerts.end}}
-
 With insufficient disk I/O, you may also see:
 
 - Degradation in [SQL response time](#service-latency).