How to Identify Java Process Executable Paths on VDIs Using ControlUp Real-Time Data and Recurring Exports

A common challenge among IT teams managing virtual desktop infrastructure (VDI) environments is identifying the exact executable paths of Java processes running on their VDI machines. In a recent inquiry, a ControlUp user sought to locate Java processes and determine the full execution path of these processes on their VDIs using ControlUp dashboards. Although they were able to create a dashboard widget that revealed the folder structure, they found no direct way to report the full executable path for historical data within ControlUp.

The root cause identified is that ControlUp does not retain the full executable path information as part of its historical data records. Instead, this level of process detail—specifically the executable path—is only available in live, real-time data monitoring. For those needing to track Java process paths over time, this limitation means historical analysis of full executable paths is not natively supported by ControlUp’s historical data collection.

Several users acknowledged that having the executable path data visible and reportable in a historical context would be highly valuable, especially for use cases such as identifying outdated Java runtime versions and understanding diverse Java process usage patterns across an organization’s VDI environment. While real-time data is sufficient for immediate troubleshooting, historical visibility would enhance trend analysis and proactive software management.

As a practical workaround, it was suggested to leverage ControlUp’s live monitoring capabilities combined with recurring data exports using the ControlUp PowerShell module command `Export-CuQuery`. By regularly exporting live process data—including executable paths—over time, teams can build their own longitudinal datasets outside of ControlUp. This approach allows filtering and analysis of Java process paths beyond what the platform currently stores in its historical database.

Regarding the broader context of Java monitoring integration into ControlUp for Azure Virtual Desktop (CU4A), current support remains focused on real-time visibility, with no confirmed release date for extending these capabilities to historical data or enhanced Java-specific monitoring features. Users are encouraged to stay updated through official ControlUp resources.

For further details on ControlUp capabilities, data export options, and dashboard customization, users may consult the ControlUp Knowledge Base at https://docs.controlup.com and the ControlUp Academy at https://cuacademy.controlup.com.

Read the entire ‘How to Identify Java Process Executable Paths on VDIs Using ControlUp Real-Time Data and Recurring Exports’ thread below:

Hello,

We have a team trying to locate java processes on VDI’s and figure out what path they are running from. I almost got it with a dashboard widget but unfortunately can’t seem to find a way to report the process exe path – just the folder structure in our controlup organization.
Is there a way to see that information by chance?

this is historical data for vdi, we do not keep the path for that. You would need to do this using live data

good one to have though

what the usecase behind this? I’m going to guess figuring out how many and where you still have outdated java runtime versions running?

This would be a vey useful dashboard

IS java monitoring still coming to CU4A?

They were looking to see historical usage of Java to get additional context. Right now, we just have the real time data, which was fine, but noticing that there are one off Java paths being called. Historical usage might make it a bit easier to identify trends.

since we don’t have it right now in cu4vdi you could do a recurring export using export-cuquery to export the live data and filter data from there

Continue reading and comment on the thread ‘How to Identify Java Process Executable Paths on VDIs Using ControlUp Real-Time Data and Recurring Exports’.  Not a member? Join Here!