How to Troubleshoot Chromebook Performance Issues
Watch this short video to learn how to quickly fix Chromebook issues with remote performance monitoring that identifies Chromebook network and application problems and their root cause.
This demo video relies on simple monitoring components that can be easily installed on Chromebooks through the Google play and Chrome web store.
Save time and resources spent on troubleshooting across the full end-to-end path from Chromebook to SaaS applications across Wi-Fi, internet, zero trust/SASE and cloud networks.
Video Transcript:
Boris Rogier:
I think Chromebook is both specifically not that specific as anyone working from home or working branches using the internet to reach SaaS applications and using security solutions around that, like cloud proxies and CASB is just going to be affected by the same thing.
So if you think, you know of the whole journey from a user to the cloud, there are so many traps from a performance standpoint. A, it's hard for someone to guess where problems actually come from. I'll show you live, when we think of experience, it's going to be driven by many factors.
It's going to be driven by very local. Networks like wi-fi and the land and which the you use and what is your IP and what is the last mile. But then you've got things that sit really in the cloud, like CASB and zero trust networks and VPNs, and potentially as the one as well if you see in branch somewhere.
And then there is where. You are getting redirected by a SaaS platform and the cloud. So the first thing we're going to show you is the digital experience and what drives it and how simply we can make this, obvious. And the second will be and that's part of the digital experience for that, for the digital experience is the hybrid connectivity.
So what is the path you take when you want to reach a certain service and how does it affect your experience?
Okay. There are three sources of information that we use to to show you data.
The first one is User-Watcher. It's a very lightweight instrumentation of your browsers. So basically you place an extension on your browser and you can deploy that industrially on all of your devices: Chromebooks or any device that has a browser. And the second one will be net Tracer which will basically be deployed on Chromebooks specifically as an Android app.
Here are the outcomes and the insights we can get from it. So I'm looking at, three days of our own team performance and digital experience. So we can see the different applications that are used. How many people actually connect to those applications? What is the connectivity?
You can see that as a figure, or you can see a trend and basically see how people might be affected, by changing conditions when they want to reach a certain application. I Good example, that would be Asana, which is the task management SaaS application we use internally, where you see latencies is changing and then you see directly indicators of user experience.
So either the time, which is to load a new page or the time needed to make an API process. An API call. So we call that API processing, and that can be broken down between the different infrastructure layer that are going to influence, the restaurant assignments that you are getting. So here you see, for example in red the waiting time, the network layer, DNS and latency are going to be represented in yellow.
Blue is going to represent the server processing. So how long the sales server or the application server is taking to respond. And green is going to. At the time, transfer data back to you. Which may be short, but may be long in some cases. Google Docs is a good example. And then you will see the number of errors that might affect your users.
The idea is that you, you get a, basically a high end view of that which application stand not so close to the users. You know which ones have experienced problems, you know which ones are affected by errors, how to glance, and then you can see your users on the map and. Where are the users that have trouble?
So for example when we look at page load times, it's obvious that the people in the western part of France have a much worse experience than people sitting in Canada, for example, in Montreal. And then we can see people by either their location. Or the internet service provider they're using to connect to different applications.
And there are are some obvious things. For example, the people using a Zero Trust network like Netskope or Microsoft zero trust network, don't get good latency that has a direct impact on their experience. And people using Orange probably inference will have a worse. Okay. So you can see that by country if there are some people sitting on site and not working remote, you can see them as well.
...