Blog

Now you can PROVE that it’s not Citrix but the backend!

You have been there: end users are complaining and your boss demands an explanation why “Citrix is slow” – again. You, the XenApp/XenDesktop admin, desperately look at Task Manager and Perfmon, but you cannot find a thing. Your servers are humming along quite nicely, but still: applications are slow, the system feels sluggish and logons are taking forever. And then, all of a sudden, things are back to normal. What was going on? How do you prevent that from happening again?

The reason for these mystery events very often lies with a backend service experiencing problems or hitting a bottleneck. If, for example, the file server is under high load, its response times are going to increase and your users will notice. Now all you need is a tool to prove that!

uberAgent reports on network performance – individually per application and per communication target. It shows you the data volume transferred and, much more importantly, the latency of each connection. Looking at the latency over time it is trivial to spot whether a particular service is currently performing subpar or not:

uberAgent-network-latency-application

Comments (2)

  1. Fahd says:

    For a MS RDS environment does it tell if and when a user session disconnected?

    1. Our dashboard “User Sessions” shows you the current state for all sessions.

      To list all users as well as the timespamp when uberAgent collected data and the session was disconnected, run the following custom search. Since uberAgent collects data every 30 seconds by default, the timestamp comes very close to the actual time of the disconnect.

      | pivot uberAgent Session_SessionDetail_Users
      latest(SessionUser) as User
      latest(SessionProtocol) as “Protocol”
      latest(SessionLogonTime) as SessionLogonTime
      latest(_time) as “Went disconnected”
      latest(host) as Host
      latest(SessionID) as “Session ID”
      sum(SessionIODurationMs) as SumSessionIODurationMs
      sum(SessionIOCount) as SumSessionIOCount
      splitrow _time
      splitrow
      SessionGUID
      filter host in (*)
      filter SessionConnectionState in (disconnected)
      | eval “Logon time”=strftime(strptime(SessionLogonTime,”%Y-%m-%d %H:%M:%S.%Q %z”), “%Y-%m-%d %H:%M:%S”)
      | eval “Went disconnected”=strftime(strptime(‘Went disconnected’, “%Y-%m-%dT%H:%M:%S.%Q%z”), “%Y-%m-%d %H:%M:%S”)
      | eval sortfield=lower(‘Logon time’)
      | sort limit=0 -sortfield
      | dedup SessionGUID
      | table
      SessionGUID
      User
      Host
      “Session ID”
      “Logon time”
      “Went disconnected”
      Protocol

      Unfortunately, we do not collect the reason why the session went to the “disconnected” state.

Leave a Reply

Your email address will not be published. Required fields are marked *