On the surface, this seems like a simple problem. In reality, it is a lot more complex than meets the eye. Many engineering applications spawn multiple windows at launch - only one of which is visible to the user - so the issues requiring a solution include:
- Which window(s) do I monitor?
- Can I monitor a window independently of the application receiving a license?
- What happens if an application window opens additional windows to expose functionality?
- Is this a generalized approach across applications and vendors?
- How do I define an active window?
- How do I avoid overwhelming my data collection process and network with window status updates?
Our development team spent a lot of time looking at multiple implementation approaches to address the above questions, before settling on a monitoring approach that is accurate, does not require customer maintenance, does not overwhelm a customer’s network and is easy for Cetrus to implement and maintain.
Why is this important? If you want to bill for application use, you need a way to account for each active/in-use window and file session for billing to the right client. If you are a service firm whose professionals work on multiple projects simultaneously, you need to report where your people are spending their time. Lastly, we intend to monitor individual browser windows in a future release, and we needed an infrastructure that would support that capability.
Want to try the next generation of application monitoring?
Send a note to firstname.lastname@example.org. We’ll answer your questions and set up a trial so you can see we’re not blowing smoke.