Last updated on NOVEMBER 01, 2016
Applies to:Oracle Communications Session Monitor - Version 2.x and later
Information in this document applies to any platform.
This can be helpful while troubleshooting a specific issue where a very detailed and granular CPU usage of specific process might need to be tracked. The atop is by default having the 10 minutes granularity. This can be lowered (see Doc ID 1986226.1) however since apid tracks the whole system's data it can get large in size with a high granularity.
Along with a CPU usage pattern tracking, there might be a need to get a backtrace of the process when it starts. This is for the engineering to be able to analyze in further detail.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms