[ISS Support Case] Detecting CPU Utilization Within Application Server
Last updated: October 17th, 2025Description
I am looking for a way to detect and monitor total CPU utilization as in how busy is the systems CPU. Preferably, it would be nice if an object could have an attribute which held the % CPU utilization on the system it is currently running on. This could then be historized. Additionally, we could create an alarm off it as well. If CPU % went above 50% for more than 30 seconds than an alarm would be created as an example. You can look at the attributes of a platform in object viewer. You can see CPULoad and CPULoadAvg listed. After reviewing these, it appears these just show the information of the current CPU core the platform is running on and not the entire CPU utilization. The platforms have an 'Alarms' tab inside the IDE with a "Report Excess CPU load alarm" option. I suspect this only reports on the current CPU core the platform is running on and not the entire CPU. Is this possible to do?
- Author: Kevin Modlin
- Published: October 17th, 2025
Details:
| Product: Application Server |
| Version: 2020 R2 |
| Solution: [Solution is visible below when you're logged in and have a current subscription] |
| Date Created: | 10/31/2022 |
| Case: | 82887 |
Recommended articles
[ISS Support Case] Synchronize Views is not working correctly in the IDE
Read More[ISS Support Case] Historian Data Gap On Appengine Failover In SP Version 2023 R2 P1
I am seeing an issue with SP2023 R2 P1 related to appengine failovers. When I cause an appengine failover, data (primarily analog) has a gap in the trend until the data changes. Sometimes the gap stays but sometimes the gap is "filled" in for some reason. I'm having a bit of a consistency issue trying to replicate this problem. Every time I cause a failover, the results are slightly different but I do see bad results. To demonstrate this, I created two videos to show what I'm seeing. If someone can create a problem ticket and reach out to me, I can forward the videos to InSource to show what I'm seeing.
Read More[ISS Support Case] MQTT setup crashes OCMC
MQTT server - CDP 2023 check encryption/validate security - no issue port validates enable user identity/try to bring certs in shuts down OCMC nothing in OCMC logs event viewer shows an app crash for mmc with cfg_mqtt_plctype1.dll as the faulting module advised repair after conferring with aveva - called client to discuss and confirm New SR960455477 (requesting) Log file Config Files Do Not upgrade Stay @ the same version of CDP Call in on 9/12/2024 No success on the MQTT server with the antivirus turned off, and it was even worse this time. Could not hook to AWS server. Proceeded to step 2, entered certificate in case it needed to log in to AWS server, but the OCMC shut down. Restarted OCMC acted strange, restarted computer. OCMC behaved normally after, but still no success with MQTT. Wants a call back whenever you're available, doesn't have to be tonight. CDP shows 2023
Read More