Application Performance Monitoring with Glue42

Performance Report - Timeline

The interop environment is often a complex one with tens or sometimes even hundreds of applications – native and web, hidden and visible. Profiling their memory consumption, debugging performance issues, or improving performance, in general, might be quite challenging and that’s why we at Glue42 introduced one more tool to the Dev tools collection – Application monitor.

The Application performance monitoring tool serves as the Glue42 dedicated Task Manager but it also offers much more!

  • Deep analysis of the performance of all the running apps
  • Detecting issues like duplicate network requests, slow or/and bad(unfulfilled) requests
  • Generating a timeline of everything happening in the apps

The main view of the Application monitor provides a quick look at all running applications (visible and service) with some useful overview as well as an indication of issues.

It is, by default, live data but can be paused at any point, cleared, or filtered so that you can focus on specific issues/s or apps.

Quick look at all running applications - live data.

The Application performance monitoring report goes deeper into the loading times and the events timeline (Framework, Glue42, browser, requests).

Performance Report - Data Grid

Another useful section of the Application performance report is the aggregated issues report with more details on what the problem is as well as a summary of the console messages.

Performance Report - Issues

Currently, the issue types that the Application monitor detects are:

  • Big Requests – When the requested resource is more than 1MB.
  • Long Requests – Request that take more than 2 sec.
  • Many Requests – Indicates when an application makes more than 15 requests.
  • Web Browser Error – Any kind of error during a request. Connection Refused/Timeout/Failed/Aborted/File too Big etc.
  • Duplicated Requests – Indicates that a request was made more than once in a single run.
  • Big Window or Activity Context – Storing big data in the context might hugely decrease the overall performance. That’s why a threshold might be set and indicated as a potential issue.
  • UI resource in Service window – Indicates when a hidden window utilizes any UI related resources such as CSS, Images, JQuery etc.
Application monitor issue detection.
Photo of Teddy Rainova
Author Details

Teddy Rainova

Former Product Manager, Glue42

Related Posts

    Blog Article

How Glue42 Provides New Technology Options

    Blog Article

User Stories: Building Workflows with Glue42 Desktop and Zapier