2 Replies Latest reply on Mar 27, 2014 9:20 AM by jhg03a

    Monitoring VMware View


      Are there any plans to add VMware VIew (VDI) specific monitoring to this platform.Being able to monitor things like:


      - connection servers

      - pools

      - desktops

      - connection statistics


      Also be able to drill down to underlying storage/network issues under the View environment.

        • Re: Monitoring VMware View

          Hi bp423,


          We are monitoring demand closely for VMware Horizon View specific use cases we can solve with our products. To that end, instead of just listing the objects you want monitored, can you help me understand what problems this would help you solve?


          Note that there are a couple of requests on the Idea Forum already for VMware View support:

          1 of 1 people found this helpful
            • Re: Monitoring VMware View

              Well, there are a few ideas that I've had.

              1. vSphere for view component status.  In the VMware view administrator summary page, they've got a simple red/green status page for each component that would be nice to know if there is a problem.
              2. Problem Desktops.  Also on the administrative summary page, there is a counter for if there are problem desktops (failed refresh, failed recompose, etc.).
              3. Tracking the peak number of concurrent users.  VMware view licensing is typically done by number of concurrent users, but it is left to the administrator to enforce the licensing limits.  It would be nice to be able to see a graph over time to see when users are logging in and how many there are for license planning purposes.
              4. Tracking ratio of desktops used per pool.  If a pool has a large number of desktops provisioned but only a small number are actively being used, that's a waste of resources that could be reclaimed by shrinking the pool size.
              5. PCoiP latency.  The success or failure of VDI implementations often has to do with the end user experience which is frequently tied to the end user response time to the virtual desktop.
              6. User login records.  If a group of 200 people are entitled to View but only 20 are using it actively, it would be nice to know who those users are for better communication and feedback.
              7. End user view client device type.  It would be nice to know what kind of device users are typically used to login to view (OSX, XP, iOS, Android, ThinClient, etc).
              8. End user view client device IP.  It would be nice to have records of what IP addresses are used to login in order to determine the geographical or network location of a user login.