Cetrus Blog

Monitoring applications is hard

Posted by Erik Hoogerhuis on Sep 29, 2015 11:41:38 AM


Monitoring desktop application usage is hard. You’d think it would be easy, because since the application has to run on a workstation or laptop, there should be lots of application-specific system related information.   

The difficulty arises because applications come in different flavors: installed on desktops, virtual delivery and partial cloud/SaaS.  In addition, software being software, every implementation rule has exceptions, requiring a generalized approach to address application “uniqueness.”

Manager and administrators want and need many data elements associated with monitoring:

  • Compliance managers want to know if the license is account for
  • Unit managers want to know how long the application is used for, who’s using it, what projects is it being used for, and is it being used most effectively
  • Licensing administrators want to know which licensing option is associated with usage
  • Procurement administrators want to know if the licenses  is perpetual, or yearly or monthly subscription and when the term is up for renewal

And so on.

Enterprises today use multiple asset management applications optimized to gather or store portions of this information. These tools don’t gather all the information needed – they only gather static information. Monitoring can add context to usage, rather than just reporting entitlement information. Contextual data includes what project(s) the application is being used for, how long the application is actually used, or what the concurrency is. Capturing these data elements requires a different type of application

In previous blog posts, we covered some issues around real-time monitoring but at a high level.  We’ll focus the next couple of posts on more specific aspects of where and how to access data needed to support the various stakeholder groups.



Posts will cover:

How to identify when an application is launched

Does the user launch the application or is it launched by another application?

Why license keys are problematic

What if the application is streamed – where is the beginning and end of the application or use session?

Is the application licensed locally, from a license server or cloud?

What if the application is browser-based?

What information is important to stakeholders: users, compliance managers, licensing managers, unit managers?

What kind of contextual information is important to stake holders?

Please come back and follow us as we dig deeper into these and other issues.



Topics: Insider