Submit a ticketCall us

Have You Auto Renewed? If not, you're missing out.
The SolarWinds Renewal Program comes with a host of benefits including the most recent product updates, 24/7 technical support, virtual instructor-led training and more. Experience all of this with the convenience of Auto Renewal, and never worry about missing any of these great benefits. Learn More.

Home > Success Center > Archive > 2017December29 - VMAN Deletes > Active recommendation: solve a memory utilization issue

Active recommendation: solve a memory utilization issue

Table of contents
No headers
Created by Lori Krell_ret, last modified by Gerald.Prado on Dec 29, 2017

Views: 368 Votes: 0 Revisions: 4

Active recommendations trigger for alerts and issues that occur in your environment and cause issues for your users. Recommendations display with a NOW flag and a clear set of resolution steps and data so you can respond quickly to verify and resolve the issue.

For example, a VM host machine in your environment triggers an active recommendation due to high memory usage. The total used memory of all the VM's on the host machine reached a critical point. To resolve, you need to move VMs to a new host.

The following example solves a memory utilization issue actively triggered and alerted in your environment:

  1. Click My Dashboard > Virtualization > Virtualization Summary.

    A list of recommendations is displayed in the dashboard. The Tokyo ESX cluster shows a critical recommendation.


  2. Select All Recommendations to open the Recommendations page.

    The Recommendations page shows a critical alert that triggered with a NOW flag. The memory utilization on host stp-esx-02.lab.tex has reached critical threshold.


  3. Click the NOW recommendation.

    In this example, the VM host stp-esx-02.lab.tex has reached 95% memory consumption. Using data compilations, the recommendation identifies the VM lab-2k8-fc-02 requires far more memory than provided by the host. Move this VM to a larger host to resolve the memory issues.


  4. Select the Power off option in the step to perform.

    The steps update to power down, move, and power up to migrate the server.


  5. Click Statistics to review the affects of the trending issue and recommended solution.

    Each step includes an expandable chart with detailed metrics that show the tracked usage and calculated resolution. The memory and CPU load is excessive and overwhelming the current host. Expand stp-esx-02.lab.tex to view details and the affects of applying the resolution.

    By moving stp-esx-02.lab.tex to a new host, the usage reduces within normal limits from 95% to 70%.


  6. Expand stp-esx-01.lab.tex to review the change and ensure they do not adversely affect the new host.

    Recommendations calculate the affects of moving VM stp-esx-02.lab.tex to the new host based on trending data over 4 weeks. The image below shows that moving the VM does not overwhelm the target host. It remains within normal limits of 65% usage for CPU and memory, a 25% increase from trending usage data for the host. See the predicted usage marked in the image below.


  7. Click Perform Now and Apply this Recommendation.

    The resolution steps begin immediately. Because this issue affects the VMs and users, scheduling the changes is not recommended unless necessary for a maintenance window.


Learn more...

To manage recommendations:

Last modified