summaryrefslogtreecommitdiffstats
path: root/health/guides/vcsa/vcsa_swap_health.md
diff options
context:
space:
mode:
authorDaniel Baumann <daniel.baumann@progress-linux.org>2024-04-19 02:57:58 +0000
committerDaniel Baumann <daniel.baumann@progress-linux.org>2024-04-19 02:57:58 +0000
commitbe1c7e50e1e8809ea56f2c9d472eccd8ffd73a97 (patch)
tree9754ff1ca740f6346cf8483ec915d4054bc5da2d /health/guides/vcsa/vcsa_swap_health.md
parentInitial commit. (diff)
downloadnetdata-be1c7e50e1e8809ea56f2c9d472eccd8ffd73a97.tar.xz
netdata-be1c7e50e1e8809ea56f2c9d472eccd8ffd73a97.zip
Adding upstream version 1.44.3.upstream/1.44.3upstream
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'health/guides/vcsa/vcsa_swap_health.md')
-rw-r--r--health/guides/vcsa/vcsa_swap_health.md35
1 files changed, 35 insertions, 0 deletions
diff --git a/health/guides/vcsa/vcsa_swap_health.md b/health/guides/vcsa/vcsa_swap_health.md
new file mode 100644
index 00000000..6e236ed3
--- /dev/null
+++ b/health/guides/vcsa/vcsa_swap_health.md
@@ -0,0 +1,35 @@
+### Understand the alert
+
+The vcsa_swap_health alert presents the swap health status of the VMware vCenter virtual machine. It is an indicator of the overall health of memory swapping on the vCenter virtual machine.
+
+### Troubleshoot the alert
+
+1. First, identify the health status of the alert by checking the color and its corresponding description in the table above.
+
+2. Log in to the VMware vSphere Web Client:
+ - Navigate to `https://<vCenter-IP-address-or-domain-name>:<port>/vsphere-client`, where `<vCenter-IP-address-or-domain-name>` is your vCenter Server system IP or domain name, and `<port>` is the port number over which to access the vSphere Web Client.
+ - Enter the username and password, and click Login.
+
+3. Navigate to the vCenter virtual machine, and select the Monitor tab.
+
+4. Verify the swap file size by selecting the `Performance` tab, and choosing `Advanced` view.
+
+5. Monitor the swap usage on the virtual machine:
+ - On the `Performance` tab, look for high swap usage (`200 MB` or above). If necessary, consider increasing the swap file size.
+ - On the `Summary` tab, check for any warning or error messages related to the swap file or its usage.
+
+6. Check if there are any leading processes consuming an unreasonable amount of memory:
+ - If running a Linux-based virtual machine, use command-line utilities like `free`, `top`, `vmstat`, or `htop`. Look out for processes with high `%MEM` or `RES` values.
+ - If running a Windows-based virtual machine, use Task Manager or Performance Monitor to check for memory usage.
+
+7. Optimize the virtual machine memory settings:
+ - Verify if the virtual machine has sufficient memory allocation.
+ - Check the virtual machine's memory reservation and limit settings.
+ - Consider enabling memory ballooning for a better utilization of available memory.
+
+8. If the swap health status does not improve or you are unsure how to proceed, consult VMware documentation or contact VMware support for further assistance.
+
+### Useful resources
+
+1. [Configuring VMware vCenter 7.0](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vcenter.configuration.doc/GUID-ACEC0944-EFA7-482B-84DF-6A084C0868B3.html)
+2. [Virtual Machine Memory Management Concepts](https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/techpaper/perf-vsphere-memory_management.pdf)