Home
The profiler is administered through a simple web interface (http://your-application/profiler), that has three main views – Profiled URLs, Profiler Results and Configuration.
The profiler does not track all requests by default; the Profiled URLs view is used to set up the application to profile specific pages / routes and the configuration view is used to configure session and sampling based profiling.
(Wildcards and regular expressions can be used to match URLs).
The screenshot below shows the profiler set up to track a single URL, across all servers, and to capture a single request trace – the Profile Count property.
The view below shows the configuration of the profiler where you can set up session and sampling based profiling as well as enabling or disabling the profiler.
Once the profiler is configured, the profiler will capture the next matching request, and the output will appear in the Profiler Results view:
Drilling into the URL will reveal individual requests, together the full trace – which includes method timings and trace debug information. The “view response” link opens up a full HTML capture of the response as seen by the client.
Additional request context information is also captured:
