Adding upstream version 1.46.3.

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

11 files changed, 359 insertions, 0 deletions

diff --git a/src/health/guides/vsphere/vsphere_cpu_usage.md b/src/health/guides/vsphere/vsphere_cpu_usage.md
new file mode 100644
index 000000000..0278edae4
--- /dev/null
+++ b/src/health/guides/vsphere/vsphere_cpu_usage.md
@@ -0,0 +1,29 @@
+### Understand the alert
+
+The `vsphere_cpu_usage` alert monitors the average CPU utilization of virtual machines in the vSphere platform. The alert is triggered in a warning state when the CPU utilization is between 75-85% and in a critical state when it is between 85-95%.
+
+### What does high CPU usage mean?
+
+High CPU usage indicates that the virtual machine's CPU resources are being heavily utilized. This can lead to performance issues, slow response times, and decreased stability.
+
+### Troubleshoot the alert
+
+1. Confirm the high CPU usage by logging into the vSphere management console and checking the CPU performance metrics for the affected virtual machine(s).
+
+2. Identify the cause of high CPU usage:
+
+   - Check the virtual machine's running processes to identify any resource-intensive applications or services. You can use the `top` command on Linux-based virtual machines or Task Manager on Windows-based virtual machines.
+   - Inspect application logs and system logs for any signs of issues, errors, or crashes that could be contributing to high CPU usage.
+   - Verify if the virtual machine has adequate CPU resources allocated. If the virtual machine is consistently using a high percentage of its allocated CPU resources, consider increasing the allocated CPU resources.
+
+3. Remediate the issue:
+
+   - If an application or service is responsible for the high CPU usage, try restarting it or addressing the specific issue causing the problem.
+   - If the virtual machine is consistently using a high percentage of its allocated CPU resources, consider increasing the allocated CPU resources or optimizing the virtual machine's performance through application and OS tuning.
+   - Monitor the CPU usage after making changes to ensure that the issue has been resolved.
+
+### Useful resources
+
+1. [vSphere Monitoring and Performance Guide](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.monitoring.doc/GUID-0C94837C-8CA4-4A4E-9694-FE9828979A77.html)
+2. [Identifying and Troubleshooting CPU Performance Issues in VMware](https://kb.vmware.com/s/article/2090599)
+3. [Optimizing Performance on Hyper-V and VMware Virtual Machines](https://info.raindanceit.com/blog/optimizing-performance-hyper-v-vmware)
\ No newline at end of file
diff --git a/src/health/guides/vsphere/vsphere_host_mem_usage.md b/src/health/guides/vsphere/vsphere_host_mem_usage.md
new file mode 100644
index 000000000..991a76f85
--- /dev/null
+++ b/src/health/guides/vsphere/vsphere_host_mem_usage.md
@@ -0,0 +1,32 @@
+### Understand the alert
+
+The `vsphere_host_mem_usage` alert is triggered when the memory utilization of a vSphere host reaches critical levels. This alert is raised to a warning level when the utilization exceeds 90% and becomes critical when it exceeds 98%. High memory utilization can lead to performance issues on the virtual machines running on the host.
+
+### Troubleshoot the alert
+
+1. Log in to the vSphere client:
+   
+   Access the vSphere client to get an overview of your host's memory utilization and to identify which virtual machines are consuming the most memory.
+
+2. Identify high memory-consuming virtual machines:
+
+   In the vSphere client, go to the "Hosts and Clusters" view and select the affected host. In the "Virtual Machines" tab, you can now see the memory usage of each virtual machine running on the host. Identify any virtual machines that are consuming a high amount of memory.
+
+3. Analyze the memory usage in the virtual machines:
+
+   Connect to the high memory-consuming virtual machines and use their respective task managers (e.g., "top" command in Linux or Task Manager in Windows) to identify the applications and processes that are causing the high memory usage.
+
+4. Take action:
+
+   - If an application or process is consuming an excessive amount of memory and is not required, consider stopping it.
+   - Alternatively, if the application or process is essential, you may need to allocate more memory to the virtual machine or consider moving the workload to a different host with more available resources.
+   - Ensure the virtual machine's memory is optimally configured, as over-allocating memory may cause contention.
+   
+5. Monitor the situation:
+
+   Keep an eye on the memory utilization of the host and the virtual machines after making changes. If memory utilization remains high, consider analyzing other virtual machines or adding more memory to the host.
+
+### Useful resources
+
+1. [vSphere Monitoring and Performance Documentation](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.monitoring.doc/GUID-115861E6-810A-43BB-8CDB-EE99CF8F3250.html)
+2. [Optimizing Memory Performance in VMware vSphere](https://blogs.vmware.com/performance/2021/04/optimizing-memory-performance-in-vmware-vsphere.html)
\ No newline at end of file
diff --git a/src/health/guides/vsphere/vsphere_inbound_packets_dropped.md b/src/health/guides/vsphere/vsphere_inbound_packets_dropped.md
new file mode 100644
index 000000000..6c3da6561
--- /dev/null
+++ b/src/health/guides/vsphere/vsphere_inbound_packets_dropped.md
@@ -0,0 +1,27 @@
+### Understand the alert
+
+This alert is triggered when a significant number of inbound dropped packets are detected on the network interface of a Virtual Machine (VM) over the last 10 minutes. It indicates a potential issue with the VM's network connectivity or performance.
+
+### What does inbound packets dropped mean?
+
+Inbound dropped packets refer to packets that are received by a network interface but discarded before they are processed by the VM. This can occur for various reasons, such as network congestion, errors in packet content, or insufficient resources to handle the incoming data.
+
+### Troubleshoot the alert
+
+1. **Check for network congestion**: High network usage can lead to packet drops when the network is saturated, or bandwidth is insufficient to handle the incoming traffic. Monitor the overall network usage in your environment to identify if this is the cause.
+
+2. **Inspect network errors**: Errors in packet content, such as checksum errors or framing errors, can result in dropped packets. Examine logs at the hypervisor and VM level for any indication of network errors.
+
+3. **Check resource usage within the VM**: Inspect CPU, memory, and disk usage within the VM. High resource utilization can lead to degraded network performance and dropped packets.
+
+4. **Verify VM network configuration**: Ensure that the VM's network configuration, such as its IP address, subnet mask, and default gateway, are correctly set. Misconfigured network settings can cause network issues, including higher rates of dropped packets.
+
+5. **Check for faulty network hardware**: Damaged or malfunctioning network hardware, such as network interface cards (NICs) or cables, can result in dropped packets. Check the hardware components involved in the VM's network connection and replace any faulty components.
+
+6. **Evaluate hypervisor performance and configuration**: The performance of the hypervisor hosting the VM can also impact network performance. Ensure the hypervisor has adequate resources and is configured correctly for optimal VM network performance.
+
+### Useful resources
+
+1. [vSphere Networking Guide](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.networking.doc/GUID-32DA33D2-7B68-471B-AF7F-0AE5456070EC.html)
+2. [vSphere Troubleshooting Guide](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.troubleshooting.doc/GUID-12989131-47E7-4005-B940-5BA5F5C089CF.html)
+3. [VM Network Troubleshooting Best Practices](https://www.vmwareblog.org/troubleshooting-vm-network-performance-part-1/)
\ No newline at end of file
diff --git a/src/health/guides/vsphere/vsphere_inbound_packets_dropped_ratio.md b/src/health/guides/vsphere/vsphere_inbound_packets_dropped_ratio.md
new file mode 100644
index 000000000..6dccfa79a
--- /dev/null
+++ b/src/health/guides/vsphere/vsphere_inbound_packets_dropped_ratio.md
@@ -0,0 +1,31 @@
+### Understand the alert
+
+This alert, `vsphere_inbound_packets_dropped_ratio`, is triggered when there is a high ratio of dropped inbound packets for the network interface in a vSphere (VMware) environment for a virtual machine. If you receive this alert, it means that the network interface is experiencing packet loss on inbound traffic over the last 10 minutes, which can result in poor network performance and degraded application functionality.
+
+### What does a high ratio of dropped inbound packets mean?
+
+A high ratio of dropped inbound packets means that a significant percentage of the incoming network packets are not being processed by the virtual machine. This can be caused by various reasons, such as network congestion, faulty hardware, incorrect network configuration, or overwhelmed virtual machine resources. A high packet loss in a network can significantly degrade its performance and affect the proper functioning of applications relying on the network.
+
+### Troubleshoot the alert
+
+1. Verify the packet loss rate
+   - Monitor the inbound dropped packets ratio using the Netdata dashboard or any other network monitoring tool you have available. Identify trends or patterns in the packet loss and try to correlate them with any specific events or changes in the infrastructure.
+
+2. Check the network congestion
+   - Examine your network traffic to determine if network congestion or high network utilization is causing the dropped inbound packets. If congestion is the issue, identify and resolve the bottleneck, such as by increasing bandwidth or optimizing the network configuration.
+
+3. Assess virtual machine resources
+   - Review the virtual machine's CPU usage, memory usage, and disk I/O. If the resources seem to be strained, consider allocating more resources or optimizing the virtual machine for better performance.
+
+4. Inspect the network hardware
+   - Check the physical network hardware, such as switches, routers, and network interface cards (NICs), for any failures or connectivity issues. Replace any faulty hardware if necessary.
+
+5. Validate network configuration
+   - Ensure that the network configuration on the virtual machine and vSphere host is correct and properly optimized for your specific environment.
+
+6. Monitor the vSphere environment
+   - Review the vSphere environment and look for any issues with the host, datastore, or other virtual machines that may be contributing to the high ratio of dropped inbound packets.
+
+7. Consult VMware documentation and support
+   - If the issue persists, refer to VMware's official documentation and knowledge base articles for further assistance, or contact VMware support for guidance.
+
diff --git a/src/health/guides/vsphere/vsphere_inbound_packets_errors.md b/src/health/guides/vsphere/vsphere_inbound_packets_errors.md
new file mode 100644
index 000000000..ef56fd6ee
--- /dev/null
+++ b/src/health/guides/vsphere/vsphere_inbound_packets_errors.md
@@ -0,0 +1,41 @@
+### Understand the alert
+
+The `vsphere_inbound_packets_errors` alert is generated when there are inbound network errors in a VMware vSphere virtual machine. It calculates the number of inbound errors for the network interface in the last 10 minutes. If you receive this alert, it indicates that your virtual machine's network is experiencing errors, which could lead to issues with network performance, reliability, or availability.
+
+### Causes of network errors
+
+There are several reasons for network errors, including:
+
+1. Faulty hardware: physical problems with network adapters, cables, or switch ports.
+2. Configuration issues: incorrect network settings or driver issues.
+3. Network congestion: heavy traffic leading to packet loss or delays.
+4. Corrupted packets: data transmission errors caused by software bugs or electro-magnetic interference.
+
+### Troubleshoot the alert
+
+Follow these steps to troubleshoot the `vsphere_inbound_packets_errors` alert:
+
+1. Log in to the vSphere client and select the affected virtual machine.
+
+2. Check the VM's network settings:
+  - Verify that the network adapter is connected.
+  - Check if the network adapter's driver is up-to-date.
+
+3. Review network performance:
+  - Examine the virtual machine's performance charts to identify high network utilization or packet loss.
+  - Use network monitoring tools, like `ping`, `traceroute`, and `mtr`, to check the network connectivity and latency.
+
+4. Inspect the physical network:
+  - Look for damaged cables or disconnected switch ports.
+  - Ensure that the network equipment, like switches and routers, is operating correctly and is up-to-date.
+
+5. Analyze system logs:
+  - Check the virtual machine's logs for any network-related errors or warnings.
+  - Investigate the vSphere host logs for issues involving network hardware or configurations.
+
+6. If errors persist, consult VMware support or documentation for further guidance.
+
+### Useful resources
+
+1. [vSphere Networking Documentation](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.networking.doc/GUID-2B11DBB8-CB3C-4AFF-8885-EFEA0FC562F4.html)
+2. [Troubleshooting VMware Network Issues](https://kb.vmware.com/s/article/1004109)
diff --git a/src/health/guides/vsphere/vsphere_inbound_packets_errors_ratio.md b/src/health/guides/vsphere/vsphere_inbound_packets_errors_ratio.md
new file mode 100644
index 000000000..b7d0af21f
--- /dev/null
+++ b/src/health/guides/vsphere/vsphere_inbound_packets_errors_ratio.md
@@ -0,0 +1,33 @@
+### Understand the alert
+
+The `vsphere_inbound_packets_errors_ratio` alert presents the ratio of inbound packet errors for the network interface of a virtual machine (VM) in VMware vSphere. If the ratio is equal to or greater than 2% and there are at least 10k packets within a 10 minute period, the alert switches to the warning state.
+
+### What are packet errors?
+
+Packet errors occur when there's an issue with the packet during transmission. Common reasons include:
+
+1. Transmission errors, where a packet is damaged on its way to its destination.
+2. Format errors, where the packet's format doesn't match what the receiving device was expecting.
+
+Damaged packets can occur due to bad cables, bad ports, broken fiber cables, dirty fiber connectors, or high radio frequency interference.
+
+### Troubleshoot the alert
+
+1. Identify the affected virtual machine and its corresponding network interface by checking the alert details.
+
+2. Inspect the network hardware by checking for any visible damage or loose connections related to the affected network interface. This may include Ethernet cables, fiber cables, and connectors. Replace or repair any damaged components.
+
+3. Check for radio frequency interference from nearby devices, such as Bluetooth devices or microwaves. If interference is suspected, move or disable the interfering devices, or consider using shielded cables for network connections.
+
+4. Monitor vSphere network performance and error metrics by using VMware vSphere's monitoring tools or other third-party monitoring software, such as Netdata. This can help pinpoint which network devices, interfaces, or protocols are causing packet errors.
+
+5. Verify that network devices and virtual machines are configured correctly to ensure optimal network performance. This may include checking Quality of Service (QoS) settings, VLAN configurations, or network resource allocation.
+
+6. Update VMware vSphere to the latest version, as well as the network drivers and firmware of the physical host, to ensure compatibility and bug fixes are applied.
+
+7. If the issue persists, consider reaching out to VMware support for further assistance.
+
+### Useful resources
+
+1. [Packet Errors, Packet Discards & Packet Loss](https://www.auvik.com/franklyit/blog/packet-errors-packet-discards-packet-loss/)
+2. [VMware vSphere Networking Guide](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.networking.doc/GUID-6DB73F20-C99A-43D4-9EE0-3277974EF8BF.html)
\ No newline at end of file
diff --git a/src/health/guides/vsphere/vsphere_outbound_packets_dropped.md b/src/health/guides/vsphere/vsphere_outbound_packets_dropped.md
new file mode 100644
index 000000000..93c508e95
--- /dev/null
+++ b/src/health/guides/vsphere/vsphere_outbound_packets_dropped.md
@@ -0,0 +1,35 @@
+### Understand the alert
+
+This alert is generated when the number of outbound `packets dropped` on a network interface of a `vSphere Virtual Machine` exceeds a specified threshold in the last 10 minutes. Packet drops are an indication of network congestion or misconfiguration, and can cause degraded performance and application slowdowns.
+
+### Troubleshoot the alert
+
+1. Identify the Virtual Machine (VM) and network interface experiencing the issue:
+   
+   Use the details in the alert to find the Virtual Machine and network interface that triggered the alert. Note the name and location of the VM and the associated network interface.
+
+2. Check for network congestion or misconfiguration:
+
+   Possible reasons for dropped packets can include network congestion, faulty network hardware, or VM configuration issues. Common ways to check for these problems are:
+
+   - Check the performance charts in the vSphere Client for the affected VM, specifically the `Network` section, to visualize the network usage, dropped packets, and other relevant metrics.
+   
+   - Verify the VM's network adapter settings are correct, such as its speed, duplex settings, and MTU size.
+   
+   - Check the VM's host machine and its physical network connections for issues, like overutilization or faulty hardware.
+   
+   - Review any network traffic shaping policies on the vSphere side, such as rate-limiters or Quality of Service (QoS) configurations.
+   
+   - Examine the VM's guest OS network settings for configuration issues, such as incorrect IP addresses, subnet masks, or gateway settings.
+
+3. Diagnose application or protocol issues:
+
+   If the network settings and hardware appear to be functioning correctly, the dropped packets could be a result of specific application or protocol issues. Inspect the network traffic to see if it's associated with certain applications. In the VM's guest OS, use tools like `tcpdump`, `wireshark`, or `iftop` to capture network packets and check for problematic patterns, or review application logs for any network issues.
+
+4. Address the problem and monitor the situation:
+
+   Once you've identified and addressed the underlying cause of the dropped packets, continue monitoring the VM's network performance to verify that the issue has been resolved. If the alert persists or the problem comes back, consider escalating the issue to the network engineering team or VMware support for further assistance.
+
+### Useful resources
+
+1. [VMware Knowledge Base - Diagnosing Network Performance Issues](https://kb.vmware.com/s/article/1004089)
diff --git a/src/health/guides/vsphere/vsphere_outbound_packets_dropped_ratio.md b/src/health/guides/vsphere/vsphere_outbound_packets_dropped_ratio.md
new file mode 100644
index 000000000..8296198f5
--- /dev/null
+++ b/src/health/guides/vsphere/vsphere_outbound_packets_dropped_ratio.md
@@ -0,0 +1,37 @@
+### Understand the alert
+
+This alert calculates the ratio of `outbound dropped packets` for a network interface on a VMware vSphere Virtual Machine over the last 10 minutes. If you receive this alert, it means your Virtual Machine may be experiencing network performance issues due to dropped packets.
+
+### What does outbound dropped packets mean?
+
+Outbound dropped packets are network packets that are discarded by a network interface when they are supposed to be transmitted (sent) from the Virtual Machine to the destination. This can be caused by several factors, such as network congestion, insufficient buffer resources, or malfunctioning hardware.
+
+### What can cause a high ratio of outbound dropped packets?
+
+There are several possible reasons for a high ratio of outbound dropped packets, including:
+
+1. Network congestion: High traffic may cause your network interface to drop packets if it cannot process all the outbound packets fast enough.
+2. Insufficient buffer resources: The network interface requires buffer memory to store and process outbound packets. If not enough buffer memory is available, packets may be dropped.
+3. Malfunctioning hardware: Issues with network hardware, such as the network adapter, could result in dropped packets.
+
+### Troubleshoot the alert
+
+- Check for network congestion
+  1. Monitor your network traffic using monitoring tools such as `vSphere Client`, `vRealize Network Insight`, or other third-party tools.
+  2. Identify whether there is an increase in traffic that could be causing congestion.
+  3. Resolve any issues related to the cause of the increased traffic to relieve the congestion.
+
+- Inspect buffer resources
+  1. Use `vSphere Client` to check your Virtual Machine's network interface settings for correct buffer allocation.
+  2. Increase buffer allocation if required or tune the buffer settings to ensure better resource usage.
+
+- Verify network hardware
+  1. Check the status of the network adapter using the `vSphere Client` or the VMware vSphere Command-Line Interface (vSphere CLI). Look for any signs of errors or issues.
+  2. Verify that the network adapter driver is up-to-date and compatible with your vSphere environment.
+  3. Consider troubleshooting or replacing the network adapter if hardware issues are suspected.
+
+### Useful resources
+
+1. [vSphere Monitoring and Performance Documentation (VMware Documentation)](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.monitoring.doc/GUID-4D4F408E-F28E-4D34-A769-EEE9D9EB02AD.html)
+2. [vSphere Administration Guide](https://docs.vmware.com/en/VMware-vSphere/index.html)
+3. [vRealize Network Insight](https://www.vmware.com/products/vrealize-network-insight.html)
\ No newline at end of file
diff --git a/src/health/guides/vsphere/vsphere_outbound_packets_errors.md b/src/health/guides/vsphere/vsphere_outbound_packets_errors.md
new file mode 100644
index 000000000..7f50579d4
--- /dev/null
+++ b/src/health/guides/vsphere/vsphere_outbound_packets_errors.md
@@ -0,0 +1,39 @@
+### Understand the alert
+
+The `vsphere_outbound_packets_errors` alert is triggered when there is a high number of outbound network errors on a virtual machine's network interface in the last 10 minutes. This alert is related to the vSphere environment and indicates a possible issue with the virtual machine's network configuration or the underlying virtual network infrastructure.
+
+### Troubleshoot the alert
+
+1. Identify the virtual machine with the issue
+
+   The alert should show you the name or identifier of the virtual machine(s) facing the high number of outbound packet errors.
+
+2. Check the network interface configuration
+
+   Verify the virtual machine's network interface configuration within vSphere. Please ensure the configuration matches the expected settings and is correctly connected to the right virtual network.
+
+3. Monitor virtual network infrastructure
+
+   Inspect the virtual switches (vSwitches), port groups, and distributed switches in the vSphere environment. Look for misconfigurations, high packet loss rates, or other issues that may cause these errors.
+
+4. Check physical network infrastructure
+
+   Investigate if there are any problems with the physical network components, such as NICs (Network Interface Cards), switches, or cables. As issues at the physical layer could also result in network packet errors.
+
+5. Examine virtual machine logs
+
+   Review the virtual machine's logs for any network-related errors or warnings. This might give you more information about the root cause of the problem.
+
+6. Update network drivers and tools
+
+   Ensure that the latest version of network drivers and VMware tools are installed on the virtual machine. Outdated or incorrect drivers can result in packet errors.
+
+7. Contact support
+
+   If you cannot resolve the issue after completing the above steps, contact your vSphere support team for further assistance.
+
+### Useful resources
+
+1. [vSphere Networking Guide](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.networking.doc/GUID-7CB8DB92-468E-404E-BC56-EC3241BFC2C6.html)
+2. [VMware Network Troubleshooting](https://kb.vmware.com/s/article/1004099)
+3. [Troubleshooting VMware Network Performance](https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/techpaper/virtual_network_performance-white-paper.pdf)
\ No newline at end of file
diff --git a/src/health/guides/vsphere/vsphere_outbound_packets_errors_ratio.md b/src/health/guides/vsphere/vsphere_outbound_packets_errors_ratio.md
new file mode 100644
index 000000000..333566ee1
--- /dev/null
+++ b/src/health/guides/vsphere/vsphere_outbound_packets_errors_ratio.md
@@ -0,0 +1,35 @@
+### Understand the alert
+
+This alert is triggered when the ratio of outbound errors for the network interface of a virtual machine in vSphere is greater than 1 over the last 10 minutes. Network outbound errors can include dropped, discarded, or errored packets that couldn't be transmitted by the network interface.
+
+### What are outbound packet errors?
+
+Outbound packet errors occur when a network interface is unable to transmit packets due to issues like network congestion, hardware problems, or misconfigurations. A high number of outbound packet errors can indicate problems in the network and affect the performance of the virtual machine, resulting in poor application responsiveness and reduced bandwidth.
+
+### Troubleshoot the alert
+
+1. Verify the virtual machine's network configuration.
+   - Check virtual machine settings in vSphere to ensure the correct network adapters are assigned and configured properly.
+   - Check the virtual machine's guest operating system network configuration for possible errors or misconfigurations.
+
+2. Monitor vSphere network performance counters.
+   - Review the network performance counters in vSphere to identify issues or bottlenecks that might be causing the outbound packet errors.
+
+3. Check the physical network.
+   - Verify the physical network connections to the virtual machine, including cabling, switches, and routers.
+   - Inspect the network hardware to ensure proper functioning and identify faulty hardware.
+
+4. Evaluate network congestion.
+   - High network traffic can cause congestion, leading to increased outbound packet errors. Evaluate the network's current usage and identify potential bottlenecks.
+   
+5. Review vSphere network policies.
+   - Check the network policies applied to the virtual machine, such as rate limiting or other traffic shaping policies, that may be causing the increased rate of outbound packet errors.
+
+6. Examine applications and services.
+   - Review the applications and services running on the virtual machine to determine if any of them are generating excessive or abnormal network traffic, resulting in outbound packet errors.
+
+### Useful resources
+
+1. [VMware: Troubleshooting Network Performance](https://www.vmware.com/support/ws5/doc/ws_performance_network.html)
+2. [vSphere Networking Guide](https://docs.vmware.com/en/VMware-vSphere/7.0/vsphere-esxi-vcenter-server-70-networking-guide.pdf)
+3. [VMware: Monitoring Network Performance Using vSphere Web Client](https://kb.vmware.com/s/article/1004099)
diff --git a/src/health/guides/vsphere/vsphere_vm_mem_usage.md b/src/health/guides/vsphere/vsphere_vm_mem_usage.md
new file mode 100644
index 000000000..0e6992149
--- /dev/null
+++ b/src/health/guides/vsphere/vsphere_vm_mem_usage.md
@@ -0,0 +1,20 @@
+### Understand the alert
+
+This alert is triggered when a virtual machine's memory usage in a vSphere environment is significantly higher than normal, indicating potential performance issues or insufficient memory allocation.
+
+### Troubleshoot the alert
+
+1. **Check memory usage**: Monitor the virtual machine's memory usage to identify potential bottlenecks or high memory consumption by applications.
+
+2. **Inspect applications**: Review applications running on the virtual machine to identify those consuming excessive memory, and determine if it's expected behavior or a memory leak.
+
+3. **Adjust memory allocation**: If the virtual machine consistently has high memory usage, consider increasing the allocated memory to improve performance.
+
+4. **Optimize applications**: Identify opportunities to optimize applications running on the virtual machine to reduce memory consumption.
+
+5. **Monitor performance**: Keep an eye on the virtual machine's performance metrics to ensure that changes in memory usage or allocation do not negatively impact performance.
+
+### Useful resources
+
+1. [VMware vSphere Documentation](https://docs.vmware.com/en/VMware-vSphere/index.html)
+2. [vSphere Performance Monitoring and Analysis](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vm_admin.doc/GUID-81E25CBB-16D9-416B-AD6F-5A96D7CD0A2D.html)