Challenges in Monitoring IGEL

The IGEL architecture comprises of many moving parts (see Figure 1) . A problem in any of these parts - whether it is a IGEL-managed or customer-managed - can ripple and affect the performance of the dependent parts, thus adversely impacting service delivery/performance. For instance, if the IGEL Cloud Gateway experiences problems, then the IGEL endpoints will be rendered unavailable for the users logging in from remote locations such as home, remote office etc. Similarly, if the IGEL Endpoints provisioned through VMs hosted on AWS or Google cloud could not be accessed, users will be denied access to their applications. This will greatly affect the user experience of digital workspaces. Likewise, if IGEL UMS experiences bottlenecks which are not resolved quickly, the IGEL endpoints that are centrally managed by that IGEL UMS will be rendered unavailable. Similarly, if one/more IGEL Endpoints are not sized with adequate resources, the endpoint performance will deteriorate, thus impacting user experience with that endpoint.

Because of these intricate inter-dependencies, whenever users complain of endpoint slowness/unavailability, administrators find it near-impossible to accurately diagnose its root-cause and resolve it. Without visibility into endpoints, IT teams will not be able to fully address “my digital workspace is slow” complaints. Endpoint monitoring completes the end-to-end picture for monitoring tools and enables fast and accurate troubleshooting of problems.

The heterogeneous vendor management stacks and the mix of on-premise, DaaS, and cloud, compound the management challenges of administrators.