Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Distinguish which of the high number of svchost processes is affected #64

Open
Jackie78De opened this issue Jan 26, 2021 · 4 comments
Open

Comments

@Jackie78De
Copy link

Hello,

I use PAL Reports frequently, but one thing that is really painful is the fact that if you have high CPU usage caused by one of the numerous svchost-processes, you actually only get a sequential number (i.e. svchost#42), but no further information.

It would be really helpful if PAL reports would collect the Process ID and the commandline parameters so that a user can find out which of the actual hosted services is causing a problem. Without that information, it's only guessing, or am I missing something? Could this be implemented?

@jeffstokes72
Copy link

jeffstokes72 commented Jan 26, 2021 via email

@jeffstokes72
Copy link

jeffstokes72 commented Jan 26, 2021 via email

@clinthuffman
Copy link
Owner

Yes, I agree that resolving the svchosts to their respective service names would be great, but unfortunately, counter logs do not contain that information. This is why I recommend using CLUE (http://github.com/clinthuffman/clue) which is my performnace data collection tool to collect the counter log, output of tasklist /svc, event logs, and ETW traces at the time of the high CPU, disk, or memory condition. CLUE is designed to be fully automatic and as low overhead as possible when collecting this data and is used frequently by Windows support teams around the world. Counter logs collected by CLUE can be analyzed by Perfmon and using the \Process(*)\ID Process, you can identify the process ID of the svchost which can be cross referenced in the tasklist output to resolve it to the service name.

@clinthuffman
Copy link
Owner

Also, the ETW trace that CLUE collects has all of the command line parameters for all of the processes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants