NeophyteDynamic thresholds would be a good solution as well.
ProfessorAs a more complex answer… I could see a way to use the current CPU load of a given process to have thresholds that push threshold adjustments for another DS on that device via the REST API in the background. Kind of a process dependent dynamic threshold rather than an averaged one like the main LM product offers. This would be a DS that would drive scripting in the background rather than being used to throw an alert. If using powershell (I’m stubbornly not learning Groovy as we use powershell throughout the entire rest of our workflow)…
get-wmiobject win32_process | where-object name -eq “nameOfYourProcess”
The returned object will give you current workload status of that process in the properties that can tell you the CPU load at the moment. If CPU > 50%, REST API for the device if DS CPU Threshold < 95% increase the CPU DS threshold. If CPU < 50% && DS CPU Threshold = 95%, lower the CPU DS threshold.
