IIS失败的请求跟踪 - 性能视图 - 不显示花费的时间 [英] IIS Failed Request Tracing - Performance View - doesn't show time spent

查看:141
本文介绍了IIS失败的请求跟踪 - 性能视图 - 不显示花费的时间的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在尝试解决网站上请求速度慢的问题,因此我配置了失败请求跟踪以触发需要10秒或更长时间的请求。我正在获取日志但是它们需要10秒以上时间,性能视图选项卡不显示花费的时间。为什么?

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?

推荐答案

我遇到同样的问题,当请求超过阈值时,似乎只保存了IIS Time Taken日志。当我根据状态代码设置跟踪时,它将始终记录.xml文件中的所有事件。尝试根据状态代码(200)创建跟踪,并将.xml的尾部与Time Taken.xml的尾部进行比较,您将看到缺少的部分。我猜这是IIS中的错误。我在Windows Server 2012 R2上使用IIS 8.5。本文提供了更多信息: http://blogs.msdn.com/b/tess/archive/2008/08/19/troubleshooting-a-performance-issue-with-failed- request-tracing-and-appcmd-in-iis7.aspx

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

这篇关于IIS失败的请求跟踪 - 性能视图 - 不显示花费的时间的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆