IIS 7 and Above
Apcmd list request (IIS8.5)
Last post Nov 10, 2018 06:40 PM by Gelede
Nov 07, 2018 10:24 PM|Gelede|LINK
Folks when i type appcmd list request i see an associated ID number for a request for example
REQUEST "36002001800003f1" (url:POST /url/url time:131000 msec, client:10.196.193.18,
The question is for troubleshooting purposes. This request number REQUEST "36002001800003f1"...does it get written to a logfile for references? or is it discarded when the request is fulfiled
Nov 08, 2018 02:55 AM|Brando Zhang|LINK
As far as I know, if you have enable the log in the IIS, it will log all the request which sent to the IIS server.
I suggest you could firstly check you have enable the logs in the IIS and check the log file to see the log details.
Nov 08, 2018 04:15 PM|Gelede|LINK
Brando, i have the logs enable. However, i need to reference the request number from the appcmd in the Logfile and that what missing. Like i said is the Request number discarded after the request is fulfilled? Again as an example appcmd request number is
"36002001800003f1". Where will i find that record? You can try it as well
appcmd list request ... you will see all pending and running request. Then try to reference or correlate the number in the Logfile
Nov 08, 2018 09:34 PM|lextm|LINK
appcmd request number is "36002001800003f1"
There is no documentation on "request number". I think that's the address of the request object in the memory, which gets lost when the request finishes.
Why do you need that for troubleshooting? Combining IIS log files, failed request tracing, network packets captured and other data you can collect, you still know which request it was and how it was processed.
Nov 08, 2018 10:17 PM|Gelede|LINK
Thanks for the update, the reason i'm curious about using the request number to troubleshoot is simple to tally how long that request took. Randomly we have been seeing issues in the IIS appcmd request queue when a particular request hold up traffic for
more than 10 minutes hence the other request are seen getting backup as well and them impacting performance to a point where the Site will freeze or slow for a few minutes or seconds during high volume. The IIS logs are big sometimes up to 20GIG... I assume
the quickest way for me is to be able to investigate the issue better is based on the request number, rather than searching thru millions of IIS records and to do time correlations.
Nov 09, 2018 03:11 AM|Brando Zhang|LINK
As far as I know, there are no request id in the iis logs.
If you want to easily locate the error or search the logs easily.
I suggest you could try to use some tool to help you analysis the logs.
For exmaple IIS Log Analyzer, Application Inslights.
Nov 10, 2018 06:40 PM|Gelede|LINK
My post exactly, if MS can log a request id/number to a logfile or ship to another place for reference. We can fix issue quicker than going extra miles