A user posed a question about measuring latency between client and server using ControlUp/Dex. The group brainstormed potential solutions and asked clarifying questions, including the type of server backend (database). The goal is to proactively identify similar cases of latency in the future.
Read the entire ‘Measuring Latency in ControlUp/Dex: How to Identify and Address Similar Cases’ thread below:
Hi, some old client-server applications we use in a virtual desktop, have compute and resource in the same on-prem datacenter and run just fine. When we move the client to an Azure workspace, the application is unacceptably slow because of the geographical separation of the client and server part. So, we know what is causing the latency but my question is: how do I measure this in ControlUp/Dex? Triggers? User Input Delay?
User Input delay is a windows client side UI metric as far as I know, so that won’t really tell you much about the latency between client app and backend server
Trying to think of ways you could determine this. We don’t do full APM, so maybe we need to think out of the box
What is the server backend? Is it a database? A webserver?
The client/server app is a Windows app, started by an execuatable. The backend is a database. The client points to the databse by ODBC. So it is just a regular Windows multi-tier app.
We know the impact when client and server are separated. We want to be able to measure this so that we can proactively recognize other similar cases.
Continue reading and comment on the thread ‘Measuring Latency in ControlUp/Dex: How to Identify and Address Similar Cases’. Not a member? Join Here!
Categories: All Archives, ControlUp One Platform, ControlUp Scripts & Triggers