Ever want to know what is really happening inside your Web server, like what requests
are executing or what AppDomains are loaded in processes? Have you wanted to trace a
request, but only when it is failing? Join this session to see how Microsoft Internet
Information Services (IIS) version 7.0 is expanding its monitoring and diagnostics
capabilities through features like runtime status and control data that enable you to
see not just which worker processes are serving which pools, but also what requests are
executing in the pools, along with their current state. Discover how you can even
monitor what module requests are in and how long they have been there. We also
show you Failed Request Tracing, a new feature that lets you configure IIS to trace
requests for a specific URL and flush those trace logs to disk if the request meets a
failure condition that you define. Find out how you can use this feature to discover
why your clients are hitting 401 errors or why a request for a static file is taking
too long. We also cover how you can instrument new managed modules and capture
that tracing in IIS 7.0 trace logs (like Failed Request Tracing), in addition to how
to route Microsoft ASP.NET page trace events into IIS trace logs. Come to this webcast
to see how IIS 7.0 enables you to finally get under the hood and see what is really
happening.
Presented by Robert McMurray
View the webcast