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 article here...
Databases Related Training & Support Archives
Databases training and support-related archives from inside the ControlUp Community on Slack.
How to Report Horizon Client Versions Across User Sessions Using ControlUp
A common requirement for managing VMware Horizon environments is the ability to report on the endpoint client versions—referred to as "HZ Client Version"—used by users to connect to the Horizon infrastructure. This need becomes particularly important in hybrid environments where users connect from both managed internal devices and unmanaged BYOD (Bring Your Own Device) endpoints. Tracking client versions helps administrators identify devices running outdated Horizon clients that require upgrades to ensure security, compatibility, and optimal performance.
Within ControlUp, the Horizon client version information can be accessed via several mechanisms. The VDI - Details view in the ControlUp console displays the HZ Client Version associated with each session, providing a straightforward way to see the current client version used. For programmatic or historical data extraction needs, ControlUp also offers a real-time data API (https://api.controlup.io/reference/gettables) which can retrieve live session details including client versions. Additionally, the "initial HZ client version" field recorded in the Session Activity report captures the client version that was used to start the session. This field, although labeled as "initial," effectively serves as a snapshot of the client version at session start.
However, because users in hybrid scenarios may connect multiple times throughout the week from different devices or update their Horizon client between sessions (for example, by disconnecting, updating, and reconnecting), it is important to consider that the client version can vary across sessions. The "initial HZ client version" is tied to each individual session start, so accumulating this information over a period allows administrators to identify all versions in use and target users on outdated clients. Pulling session activity reports over time and correlating the client versions used enables identification of BYOD devices needing updates even if the same user connects from multiple endpoints.
In summary, the "initial HZ client version" contained in ControlUp’s Session Activity reports is the key field for tracking Horizon client versions across user sessions. The ControlUp real-time data API further facilitates custom querying and automation for this reporting. For detailed exploration of session data, the VDI - Details view complements these options with an at-a-glance interface. Using these tools, administrators in hybrid environments are able to efficiently monitor and manage Horizon client versions on both managed and BYOD devices, ensuring compliance and performance consistency.
Read the entire article here...
Read the entire article here...
Understanding ControlUp’s App Catalog List
A user asked if there is a maintained list of apps that are covered under ControlUp's app catalog. The list is pulled from their back end database and it is best practice to include all apps at scoping. This information cannot be copied easily and there is not a public list available as it can change daily.
Read the entire article here...
Read the entire article here...
Addressing Timestamp Issues in ControlUp’s PowerShell Cmdlet Invoke-CUQuery
A user is experiencing an issue with the PowerShell cmdlet Invoke-CUQuery and discusses it in a Slack conversation with @members. They expected a timestamp to change whenever a value changes, but this is not the case. They share a screenshot of the issue and mention their understanding of the documentation. Another user explains that whenCreated reflects when a computer record was created in the internal database and gives a recommendation for a better approach. The original user shares their use case for needing a timestamp that shows when a record was last changed, but is informed that this data is not currently available. Other potential solutions and a discussion take place.
Read the entire article here...
Read the entire article here...
Understanding CPU Max in ControlUp Performance View
A user asked for clarification on the CPU utilization graphs in the User Session Details / Performance view. Another user explained that the CPU Max graph shows the highest 3-seconds sample during a 5-minute period, which can cause spikes of 100% even if the host and user CPU numbers are only at 10%. The original user was directed to the documentation for further explanation.
Read the entire article here...
Read the entire article here...
Widget Wednesday #5: Troubleshooting “No Data Available” in Dashboards
In this episode of Widget Wednesday, Chris Twiest tackles a question almost every dashboard builder encounters at some point: why does a widget show “no data available”? The session focuses on practical troubleshooting techniques to help identify the root cause quickly and restore meaningful data in ControlUp dashboards.
Read the entire article here...
Read the entire article here...
Modifying the Analyze Logon Duration Script for JSON Output
A member asked for help with modifying the analyze logon duration script to output json instead of a text file. Another member offered a modified version from a year ago and will set a reminder to share it tomorrow, with the original use case being to send the data to CU4D for processing. The modifications are between lines 5017 and 5290, but a call can be arranged to simplify it if needed.
Read the entire article here...
Read the entire article here...
Creating Expressions and Dashboards in ControlUp
The user is inquiring about the creation of expressions in ControlUp, specifically trying to create a dashboard for CU customers. Another user suggests the use of CU Workflows to gather data and create custom indices for dashboarding. While a suggestion is made to potentially use Expert Builder, it is confirmed that this functionality is not available in filtering.
Read the entire article here...
Read the entire article here...
Monitoring NIC Dropped Packets in ControlUp
A user asked about viewing historical information for NIC dropped packets, but it is not stored in the historical database. They explored creating triggers to monitor it, but it did not seem to be the root cause. They ended the discussion wishing everyone a great day.
Read the entire article here...
Read the entire article here...
Understanding ControlUp Monitor Database and Query Options
There were questions about where the ControlUp monitor database is stored and what tables are available. It was suggested that the database is stored in RAM and data is only exported to the cloud backend for long enough. There were suggestions to use the powershell invoke-cuquery or api to query the database. It was also mentioned that the export-cuquery may have less impact on the monitor and export more data at a time.
Read the entire article here...
Read the entire article here...