You should be able to enable page-level tracing features. This was available after ASP.NET 1.1, and you included it by adding a property to the page directive - for example.
<%@ Page Language="vb" AutoEventWireup="false" Trace="true" Codebehind="whatever.aspx.vb" Inherits="Example.Whatever"%>
You can also include it from code. I usually put it in code behind the page load event, so I can include it based on the custom attribute of the query string.
If Request.QueryString("trace") = "true" Then Trace.IsEnabled = True End If
Of course, this code should be removed before deployment to production.
I'm not sure if this is what you are looking for - since you mention that reports and tracing are usually used as a debugging tool, but it has a lot of information that you can use to troubleshoot page performance.
Nikhil
source share