Hello,
Is it possible to profile remote IIS services (w3wp.exe) using the API?
Profile remote IIS server using API
-
- Posts: 6172
- Joined: Wed Aug 11, 2004 8:37 am
Re: Profile remote IIS server using API
Hello sandeep
Yes.
IIS should be started with the profiler on the remote machine:
http://www.yourkit.com/docs/net70/help/ ... remote.jsp
To connect to a remote process via the API, create the controller with "new Controller(host, port)"
http://www.yourkit.com/docs/net70/help/api.jsp
Best regards,
Anton
Yes.
IIS should be started with the profiler on the remote machine:
http://www.yourkit.com/docs/net70/help/ ... remote.jsp
To connect to a remote process via the API, create the controller with "new Controller(host, port)"
http://www.yourkit.com/docs/net70/help/api.jsp
Best regards,
Anton
-
- Posts: 24
- Joined: Wed May 16, 2012 3:08 pm
Re: Profile remote IIS server using API
Thanks Anton,
Is there any way to restrict profiling to only IIS worker (w3wp.exe) processes instead of attaching the profiler to all .NET applications? I don't see a function to attach the profiler from API when needed Is there any way to do that?
Is there any way to restrict profiling to only IIS worker (w3wp.exe) processes instead of attaching the profiler to all .NET applications? I don't see a function to attach the profiler from API when needed Is there any way to do that?
-
- Posts: 6172
- Joined: Wed Aug 11, 2004 8:37 am
Re: Profile remote IIS server using API
There is no explicit way to do it, but I can suggest the following workarounds:
- As the documentation says, a system environment variable COR_ENABLE_PROFILING must be set to 1 in order to enable IIS service profiling. You can re-define the same variable at user level e.g. by setting it to 0. This will at least limit the set of profiler enabled applications to services only.
- Change the profiler agent's access rights such that only IIS's user can load it
- As the documentation says, a system environment variable COR_ENABLE_PROFILING must be set to 1 in order to enable IIS service profiling. You can re-define the same variable at user level e.g. by setting it to 0. This will at least limit the set of profiler enabled applications to services only.
- Change the profiler agent's access rights such that only IIS's user can load it