Options
How do you profile a .NET Core website (REST API) running under IIS?
krue
Posts: 3 Bronze 1
Specifically, this is a REST API, and I need to profile how it reacts as other client sites call into the APIs it offers.
I envision a solution of specifying the URL to my .NET Core REST API that I have hosted in IIS, with a button to start profiling, which I would click, and it would restart IIS (like it does when you do "IIS - ASP.NET"), and begin profiling the website. Presumably it would stay running (just like an IIS website), and then I could launch my client site that calls into the REST API, and those calls would be profiled.
I've seen lots of responses about how to profile a .NET Core application, or even a website, but nothing about how to do this for a .NET Core website running under IIS. And it is even more problematic that the website is a REST API, and isn't directly a website with pages in the traditional sense.
It is also interesting that when you start a new profiling session, you have the option for "IIS - ASP.NET", but nothing for "IIS - .NET Core website". There is also a ".NET executable", and "Attach to .NET 4+ process", but not "Attach to .NET Core process"
I asked this earlier under the question "ant profiling .net api", back on September 9th, 2019, but never received an answer.
With the direction that architectures are going, this HAS to be a very common situation.
Any help would be appreciated.
I envision a solution of specifying the URL to my .NET Core REST API that I have hosted in IIS, with a button to start profiling, which I would click, and it would restart IIS (like it does when you do "IIS - ASP.NET"), and begin profiling the website. Presumably it would stay running (just like an IIS website), and then I could launch my client site that calls into the REST API, and those calls would be profiled.
I've seen lots of responses about how to profile a .NET Core application, or even a website, but nothing about how to do this for a .NET Core website running under IIS. And it is even more problematic that the website is a REST API, and isn't directly a website with pages in the traditional sense.
It is also interesting that when you start a new profiling session, you have the option for "IIS - ASP.NET", but nothing for "IIS - .NET Core website". There is also a ".NET executable", and "Attach to .NET 4+ process", but not "Attach to .NET Core process"
I asked this earlier under the question "ant profiling .net api", back on September 9th, 2019, but never received an answer.
With the direction that architectures are going, this HAS to be a very common situation.
Any help would be appreciated.
Tagged:
Answers
Jessica Ramos | Product Support Engineer | Redgate Software
Have you visited our Help Center?