A user is asking for ways to measure latency in ControlUp. The possible solutions suggested are using Scoutbees (if configured), ping and tracert scouts, Web Application scouts, and Site load measurement. One user asks if it can be used to measure the latency of an executable, but the application in question is an old Windows app without a web URL. The discussion continues about similar threads on the topic.
Read the entire ‘Measuring Latency in ControlUp: Solutions and Confusion Over Windows Applications’ thread below:
Hi, some 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, de application turns 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?
do you have Scoutbees?
Yes, we do but is not configured yet, we only have ControlUp for two months now.
there are ping and tracert scouts as well as Web Application scouts. The Site load might work well too.
Can this be used to measure the latency of an executable? The client-server applicaties is a Windows application: a Windows client and a database in the backend.
does it have a web url?
It’s an old Windows application, no web url.
It is packaged as an App-V.
Oh, I notice that there are 2 threads on the same topic
Continue reading and comment on the thread ‘Measuring Latency in ControlUp: Solutions and Confusion Over Windows Applications’. Not a member? Join Here!
Categories: All Archives, ControlUp Synthetic Monitoring