I'm trying to troubleshoot slows requests on a website so I have configured Failed Request Tracing to trigger for requests taking 10 seconds or more. I'm getting logs but though they take 10+ seconds the performance view tab doesn't show where the time is spent. Why is that?
相关问题
- How to make a .svc file write to asp.net Trace.axd
- How to deploy python flask application in conda ba
- ASP.NET won't compile to debug
- Web server farms with IIS ? Basic Infos [closed]
- how do i manually configure a virtual directory in
相关文章
- 请教IIS URL重定向的问题
- 一个愚昧的问题,在一台电脑/云服务器下,假设某个系统访问量大,给他在IIS部署多个同样的网站和部署一
- .Net5 程序发布到IIS10
- 程序是如何接收并启动监听 IIS 站点设置的端口号的?
- IIS App Pools & Static Classes
- ASP.NET code to detect whether IIS “Windows Authen
- Installing Web Deploy on IIS 7+ with Shared Config
- ASP.NET is not authorized to access the requested
I have the same problem and it seems that IIS Time Taken logs are saved only up-to point when the request exceeds threshold. When I set up tracing based on status code, it will always log all events in .xml file. Try to create trace based on Status code (200) and compare tail of .xml with tail of "Time Taken" .xml and you will see missing part. I guess that it's bug in IIS. I'm using IIS 8.5 on Windows Server 2012 R2. More information is in this article: http://blogs.msdn.com/b/tess/archive/2008/08/19/troubleshooting-a-performance-issue-with-failed-request-tracing-and-appcmd-in-iis7.aspx