A user was having difficulty identifying a CPU-heavy app in their VDI. They realized that the App Trends report was showing an average, which was being skewed by multiple instances of the same app with only one of them using significant CPU. To address this, ControlUp is expanding their VDI Streaming REST API to allow for pulling process data with filters. Users can contact their CSM/TSM or open a support ticket for assistance.
Read the entire ‘Improving App Identification in ControlUp VDI with Expanded Streaming API’ thread below:
I’m hunting down an app that’s being a cpu hog in our VDI. In Machine Trends I see the high cpu utilization in the chart, and my suspect app at the top of each data point. However, under App Trends, I don’t see the cpu utilization there.
The app runs multiple processes with the same name but only 1 of those is chewing up cpu at a time, leaving 10+ other 0% cpu processes to drop the average in App Trends charts. I missed this a few times not realizing what was happening. I’d check App Trends but cpu looked minimal, so I’d move on.
We included this app in our process data collection rules because we wanted full data on it. Would removing it from data collection reduce the white noise to better draw out the extremes?
Hi @member, the default CPU threshold for processes in the process reduction feature is 1% CPU, so I suggest you keep this process in the data collection rule so you have the full dataset. Indeed the App Trends report will use all the instances of the processes so the Avg. will “flat” the numbers. Having said that, that are two things that can help here:
- When using App Trends, you can click on a single data point, to see the distribution of all app instances and also see top consumers. That’s a great way to see more granular data based on specific process instances in any given 5-min data point:
- we are now expanding our VDI Streaming REST API to allow customers to pull data directly from the SQL back-end, and enable pulling process data using filters (for example, get all Tanium.exe processes where CPU > 5%)
Our PS team can probably assist with this, while we are working on the public API’s. If you have a CSM / TSM, please raise the request with them, otherwise, please open a support ticket and mention this thread
Continue reading and comment on the thread ‘Improving App Identification in ControlUp VDI with Expanded Streaming API’. Not a member? Join Here!
Categories: All Archives, ControlUp for VDI