{"id":40699,"date":"2026-09-25T10:50:08","date_gmt":"2026-09-25T14:50:08","guid":{"rendered":"https:\/\/www.eginnovations.com\/blog\/?p=40699"},"modified":"2026-09-25T11:11:41","modified_gmt":"2026-09-25T15:11:41","slug":"amazon-workspaces-applications-in-console-monitoring","status":"publish","type":"post","link":"https:\/\/www.eginnovations.com\/blog\/amazon-workspaces-applications-in-console-monitoring\/","title":{"rendered":"Amazon WorkSpaces Applications In-Console Monitoring"},"content":{"rendered":"
\n

Recently, Amazon announced WorkSpaces Applications in-console monitoring<\/a>. This is a big shift forward for AWS, who is quietly building market share with their Amazon WorkSpaces Applications (previously called Amazon AppStream 2.0<\/a>) virtual applications offering. This announcement validates that observability matters for Amazon WorkSpaces Applications customers \u2013 they need to see what\u2019s going on in their virtual application and desktop fleets, hosts and sessions.<\/p>\n

Amazon AppStream 2.0 vs Amazon WorkSpaces <\/span>Read the blog<\/span><\/span>\"\"<\/a><\/p>\n

<\/span>Amazon\u2019s Observability Gap<\/span><\/h2>\n

Until now, all the popular digital workspace<\/a> technology vendors had a native observability offering. Citrix has several tools including Citrix Director<\/a>, Citrix Uber Agent, Citrix Analytics and so on to cover different observability needs for customers. Microsoft Azure offers Azure Monitor<\/a> for collecting metrics about the Azure Virtual Desktop service. Omnissa<\/a> offers Workspace ONE for DEX and Omnissa Monitor for infrastructure monitoring. In comparison, Amazon had no out of the box dashboard for monitoring Amazon WorkSpaces Applications Sessions and hosts.<\/p>\n

Over the last year, Amazon has added capabilities to cover the gap to an extent. The in-console monitoring graphs provide an automatic CloudWatch dashboard<\/a> with graphs created the moment you configure the service. Previous enhancements a few months earlier deliver CloudFormation templates<\/a> for fleet-level and per-user dashboards, and a template that stands up six CloudWatch alarms with SNS<\/a> email notification against a named fleet.<\/p>\n

These investments are a signal that streamed application delivery is now business-critical and customers are asking hard questions about user experience, and AWS has answered with better native instrumentation and dashboarding.<\/p>\n

So, the question for anyone running Amazon WorkSpaces Applications at any reasonable scale (hundreds to thousands of users) is what falls outside its frame, and whether that gap matters in your environment. Spoiler alert \u2013 it probably does.<\/p>\n

\"Screenshot<\/a><\/p>\n

Figure 1: How the new metrics are displayed within the AWS WorkSpaces Applications portal.<\/div>\n

<\/span>What The Native Amazon Tooling Gives You For Monitoring Amazon WorkSpaces Applications<\/span><\/h2>\n

This native tooling is a start. It includes the details below:<\/p>\n

\n\n\n\n\n\n
\n Fleet capacity metrics for capacity decisions and scaling alarms\n <\/th>\n\n ActualCapacity, AvailableCapacity, DesiredCapacity, InUseCapacity, PendingCapacity, CapacityUtilization, and InsufficientCapacityError \u2014 plus the session-slot equivalents for multi-session fleets and three drain-mode metrics.\n <\/td>\n<\/tr>\n
\n Instance and session performance\n <\/th>\n\n CpuUtilizationInstance, MemoryUtilizationInstance, PagingFileUtilizationInstance, DiskUtilizationInstance, DiskReadOperations, DiskWriteOperations, and the per-session CPU and memory equivalents.\n <\/td>\n<\/tr>\n
\n Session quality\n <\/th>\n\n InSessionLatency, UDPPacketLossRate, TCPRetransmissionRate, Bandwidth, BandwidthInbound, CongestionWindow, ConnectionDuration, and FramesPerSecond. Dimensions run down to [FleetName, InstanceId, SessionId, UserId], so you can find an individual user’s session.\n <\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

For an administrative, native tooling helps them answer the operational questions such as \u201cwho is logged in\u201d, \u201cwhat resources are they consuming\u201d, \u201cwhat latency are they experiencing\u201d, \u201cis there a resource crunch on the session hosts\u201d, etc. User session vs. host metrics can be seen together without needing any setup and configuration.<\/p>\n

<\/span>Where the Gap in Amazon WorkSpaces Applications Monitoring Really Exists<\/span><\/h2>\n

Three boundaries define what the AWS\/AppStream namespace can and cannot tell you. Not flaws, but consequences of what the service is instrumented to observe.<\/p>\n

1.<\/span><\/p>\n

<\/span>The metrics describe the session, not the complete user experience<\/span><\/h2>\n<\/div>\n

Go through the full published metric set \u2014 single-session fleet usage, multi-session fleet usage, and instance and session performance \u2014 and there is no logon duration metric. No application launch time. No user input delay. No profile load time. No GPU metric of any kind.<\/p>\n

That matters because it is based on user experience where users form their judgement of the service. For example, logon is the single most common source of “it’s slow” tickets in any streamed environment. A session that starts in eleven seconds and one that starts in ninety seconds produce identical ConnectionDuration and InSessionLatency readings once the user is in. The pain happens before the metrics start.<\/p>\n

The same applies inside the session. CpuUtilizationSession tells you the session is consuming 94% of allocated compute. It does not tell you which application is doing it, or which user process to look at. For graphics-heavy workloads \u2014 CAD, imaging, video \u2014 the absence of GPU metrics leaves the most expensive part of the instance un-instrumented.<\/p>\n

eG Enterprise measures all aspects of user experience. eG Enterprise measures logon as a broken-down sequence, tracks application launch time and user input delay per session, identifies the processes and applications consuming CPU, memory and GPU inside the instance, and reports Amazon DCV<\/a> (was NICE DCV) protocol metrics per session \u2014 including bandwidth by virtual channel, so you can see whether a user’s problem is display, audio, clipboard or file redirection. And the data is available in real-time and historically. The new Amazon WorkSpaces Applications dashboard shows the sessions and hosts that are currently active, not ones that were present a few hours ago.<\/p>\n

\"Screenshot<\/a><\/p>\n

Figure 2: Login breakdowns for Amazon WorkSpace Applications users are added to rich overview dashboards.<\/div>\n

\"Screenshot<\/p>\n

Figure 3: Detailed breakdowns of every login to Amazon WorkSpaces Applications session are included in the eG Enterprise platform.<\/div>\n
2.<\/span><\/p>\n

<\/span>The metrics stop at the AWS account boundary<\/span><\/h2>\n<\/div>\n

This is the larger point, and it is the one that decides most evaluations.<\/p>\n

A streamed application is delivered by a chain. Some of that chain runs in your AWS account, but so much of it doesn\u2019t: Active Directory, whether on-premises or hybrid, the identity provider handling SAML, print servers, etc. The line-of-business middleware the streamed application connects back to is quite often still on-premises. Direct Connect or the site-to-site VPN carrying that traffic affects user experience as well. And at the far end, the user’s endpoint, their local network, and their home Wi-Fi.<\/p>\n

CloudWatch metrics for WorkSpaces Applications are dimensioned by Fleet, InstanceId, SessionId and UserId. They cannot report on a domain controller in your data centre, a profile share that has run out of IOPS, or a Direct Connect circuit that is saturated at 4pm on a Tuesday. Those components will still ruin the user’s day.<\/p>\n

This is the single strongest reason to run a platform-independent monitoring layer alongside native tooling. eG Enterprise integrates with CloudWatch to collect the AWS-native metrics and monitors the rest of the chain in the same console \u2014 profile servers, Active Directory, storage, network, the on-premises application and database tiers, and the endpoint itself. Over 650 application and infrastructure technologies are supported<\/a> from a single console.<\/p>\n

\"Screenshot<\/a><\/p>\n

Figure 4: eG Enterprise is proven for monitoring deployments at scale of Amazon WorkSpaces Applications.<\/div>\n
3.<\/span><\/p>\n

<\/span>Collection is not correlation<\/span><\/h2>\n<\/div>\n

Native tooling gives you accurate numbers. What it does not do is tell you which number caused the others.<\/p>\n

When InSessionLatency climbs and FramesPerSecond drops and CpuUtilizationInstance spikes, you have three alarms and a triage problem. Somebody senior now spends an hour working out the order of events. Industry service management experience puts roughly 80% of the time between a problem occurring and its resolution into isolating the cause \u2014 only about 20% goes on the fix.<\/p>\n

eG Enterprise applies patented auto-correlation<\/a> across every layer of every tier, with machine-learning auto-baselining<\/a> to establish what normal looks like without administrators hand-setting thresholds. It separates cause from effect and points at the origin. Automated diagnosis fires in context and stores the detail, so post-mortem analysis does not depend on the affected instance still being available.<\/p>\n

4.<\/span><\/p>\n

<\/span>No users means no metrics<\/span><\/h2>\n<\/div>\n

Instance and session metrics are collected at a five-minute interval, and the first data point appears within five minutes of a session being provisioned. Sensible \u2014 but it means the metrics only exist when someone is already logged in. At 5am, before the first shift, the service could be broken and the dashboards would be quiet.<\/p>\n

The eG AWS Logon Simulator targets the WorkSpaces Applications web client logon URL from a standard Chrome desktop and launches applications on a schedule, 24×7, at whatever interval you set. It needs no script recording. When a step fails, it names the failing step. It works against multi-session and single-session fleets. Run it from several locations and you also get a read on geographic differences in logon performance.<\/p>\n

\"Screenshot<\/a><\/p>\n

Figure 5: The eG Enterprise Logon Simulator for AWS WorkSpaces Applications will proactively monitor logon performance 24×7 even when no real users are accessing applications. Issues such as long application launch times can easily be identified as well as logon failures.<\/div>\n

\"Clickable<\/a><\/p>\n

5.<\/span><\/p>\n

<\/span>Most organizations do not run one platform<\/span><\/h2>\n<\/div>\n

eG Innovations survey data<\/a> found 54% of organizations have deployed more than one digital workspace technology. If you run WorkSpaces Applications alongside Citrix, Azure Virtual Desktop, Windows 365 or Omnissa Horizon, native tooling gives you a console per platform, each with its own metrics, thresholds and reports, and no shared view.<\/p>\n

eG Enterprise reports consistent user experience metrics across all of them in one console. That also makes migration measurable: baseline the incumbent platform before you move, compare after, and hold the business case to account with data rather than assertion.<\/p>\n

\"Screenshot<\/a><\/p>\n

Figure 6: eG Enterprise can provide simple geographic location overviews across large Amazon WorkSpaces Applications deployments.<\/div>\n
6.<\/span><\/p>\n

<\/span>Observability for all Stakeholders<\/span><\/h2>\n<\/div>\n

While aggregating logs and metrics across tenants is possible with AWS CloudWatch, it is not the easiest. Often, operating an AWS digital workspace involves liaising with multiple IT experts. Furthermore, IT executives need insights into digital workspace usage and performance. In a managed services context, individual tenants need their respective views. Unlike, AWS CloudWatch which is not ideal to operate in an MSP context, eG Enterprise is fully multi-tenant and supports role-based access control. While MSPs get complete visibility across all tenants, each tenant gets a read-only view of their environment in real-time and for historical analysis. Role-based access can be provided to architects, executives, helpdesk and so on.<\/p>\n

\"\"<\/a><\/p>\n

Figure 7: User productivity analysis in an Amazon WorkSpaces deployment.<\/div>\n

\"\"<\/a><\/p>\n

<\/span>The Benefits of Amazon WorkSpaces Applications Monitoring with eG Enterprise<\/span><\/h2>\n

\"\"\"\"A global banking client with several existing monitoring tools measured the change after deploying eG Enterprise. Within eight weeks, time to identify and resolve routine day-to-day performance problems fell by 25\u201333%. Time to resolve complex multi-domain problems fell by an order of magnitude. The same organization recorded a 15% reduction in technical support staffing levels across a 200-application deployment.<\/p>\n

eG Innovations holds AWS Digital Workplace Competency<\/a> status \u2014 one of a small number of observability vendors to have done so \u2014 and the eG Enterprise SaaS platform is certified against the AWS Well-Architected Framework<\/a>.<\/p>\n

You can find eG Enterprise Cloud a SaaS offering on the AWS marketplace, here<\/a>. For on-premises and self-hosted cloud deployment options, please contact us<\/a> directly.<\/p>\n

\"\"<\/a><\/p>\n

<\/span>Where To Start With Amazon WorkSpaces Applications Monitoring<\/span><\/h2>\n

Keep native dashboards for capacity and scaling.<\/p>\n

The useful test is narrower and takes about a fortnight: pick one fleet, run the logon simulator against it around the clock, connect eG Enterprise to your CloudWatch metrics, and add the non-AWS dependencies \u2014 Active Directory, profile storage, the network path, the back-end application. Then compare what you can explain in two weeks against what you could explain the fortnight before.<\/p>\n

If your team is spending real hours a week on streamed application performance tickets they cannot close quickly, that comparison will settle the question either way.<\/p>\n

Trial eG Enterprise in your environment today. Visit https:\/\/www.eginnovations.com\/<\/a> and click Free Trial to register.<\/strong><\/p>\n

<\/span>Related Information<\/span><\/h2>\n