Hi Cubiaz55,
Your approach will depend on the DEM tool available to you (Standard, Pro or Enterprise). I will also reference the Trust Portal. I will try to keep the information below high-level. I’m happy to clarify anything that may be confusing:
For question 1: Which DEM graph is the most useful to investigate performance?
In DEM Standard, I would start with the Tenant Overview menu and filter by POP and application to understand the client to POP and POP to app latencies for all users. You will have a general idea of segment latencies, but you will not be able to get more granularity than that. For example, you will not be able to see which users specifically are seeing longer latencies.
The Trust Portal can give you insight into Netskope service status.
In DEM Pro, in the User Overview menu, I would start by filtering for context (per application, per POP, per location). Once I know if the issue is related to an application, for example, I would identify the users going to this app with the lower experience scores, and then use the User Drill-down view to identify the root cause.
Another option, in DEM Pro, if you know which user(s) are seeing the slowness, you can drill down into each specific user and identify if it’s the device, the client-to-POP network, if it’s Netskope or the POP-to-app segment causing the degradation.
In DEM Enterprise, I would start by comparing the performance by site and application for the last 30 days. I would quickly know if the issue is limited to a site or an app, and if it is coming from the application side, Netskope or the network side. Depending on the issue, I will then be able to truly identify the root cause. For example, if it is the app, I will be able to identify which server at fault. If it is an ISP issue, I will be able to signal the misbehaving node(s).
Regarding question 2, which graph are you looking at?
Hi Cubiaz55,
Your approach will depend on the DEM tool available to you (Standard, Pro or Enterprise). I will also reference the Trust Portal. I will try to keep the information below high-level. I’m happy to clarify anything that may be confusing:
For question 1: Which DEM graph is the most useful to investigate performance?
In DEM Standard, I would start with the Tenant Overview menu and filter by POP and application to understand the client to POP and POP to app latencies for all users. You will have a general idea of segment latencies, but you will not be able to get more granularity than that. For example, you will not be able to see which users specifically are seeing longer latencies.
The Trust Portal can give you insight into Netskope service status.
In DEM Pro, in the User Overview menu, I would start by filtering for context (per application, per POP, per location). Once I know if the issue is related to an application, for example, I would identify the users going to this app with the lower experience scores, and then use the User Drill-down view to identify the root cause.
Another option, in DEM Pro, if you know which user(s) are seeing the slowness, you can drill down into each specific user and identify if it’s the device, the client-to-POP network, if it’s Netskope or the POP-to-app segment causing the degradation.
In DEM Enterprise, I would start by comparing the performance by site and application for the last 30 days. I would quickly know if the issue is limited to a site or an app, and if it is coming from the application side, Netskope or the network side. Depending on the issue, I will then be able to truly identify the root cause. For example, if it is the app, I will be able to identify which server at fault. If it is an ISP issue, I will be able to signal the misbehaving node(s).
Regarding question 2, which graph are you looking at?
For question 2, I am looking at the “Publisher CPU Usage” graph under NPA.
