I often get alerts showing CPU reached 100%. This is good, however by the time I get to looking at the issue, it's gone. How can I go "back in time" to determine what process was causing my CPU to spike?
Hu snydosaurus
Generally speaking, you'll need to be monitoring the process or service for SAM to give you a heads up as to whether any given component is causing the CPU spike. All you'll see is when it was high from the CPU statistic history graphs.
I have a Powershell template i use in SAM to deal with this scenario
CPU/MEM Process Snapshot
