I am guessing that those files never make it to the processing time report, 
since the ASP hangs, it probably never finishes the HTML return to the client, 
hence status 500 errors. 

Brings back (fond?) memories of searching logs for 500 errors to help find bad 
ASP code. :-) 

Apologies if this is too obvious, but do you have the Failure Report on? I 
believe it will show you which files failed, but I don't remember if correlates 
it to a status code. 

Hope that helps some... 

Glenn 


----- Original Message ---- 
From: Jeff Wilkinson 
To: [email protected] 
Sent: Tuesday, August 8, 2006 12:40:03 PM 
Subject: [analog-help] Re: Is there a way to see what files have high 
processing times? & when? 


Jeff Wilkinson writes: 

whoops, sorry to followup my own email, but I forgot 
to ask this: 

Is there any way to get more detail on the Status 
report? or to perhaps do a report where you only 
include by status? 

Thinking a requests report that only includes 
files with status "500 Internal server error" 
might be real handy... 

yes, I did see the notes in the docs that mention 
that almost all the reports only show data on 
successful hits, and that analog isn't real useful 
for failure analysis... sigh. 

thanks, 
jeff 
-- 
Jeff Wilkinson 
[EMAIL PROTECTED] 




+------------------------------------------------------------------------ 
| TO UNSUBSCRIBE from this list: 
| http://lists.meer.net/mailman/listinfo/analog-help 
| 
| Analog Documentation: http://analog.cx/docs/Readme.html 
| List archives: http://www.analog.cx/docs/mailing.html#listarchives 
| Usenet version: news://news.gmane.org/gmane.comp.web.analog.general 
+------------------------------------------------------------------------
+------------------------------------------------------------------------
|  TO UNSUBSCRIBE from this list:
|    http://lists.meer.net/mailman/listinfo/analog-help
|
|  Analog Documentation: http://analog.cx/docs/Readme.html
|  List archives:  http://www.analog.cx/docs/mailing.html#listarchives
|  Usenet version: news://news.gmane.org/gmane.comp.web.analog.general
+------------------------------------------------------------------------

Reply via email to