Message Analyzer不解析WPP实时跟踪 [英] Message Analyzer does not parse WPP live traces
问题描述
我正在使用Message Analyzer 1.0.2(官方版本中也存在此问题)。
当我捕获WPP日志并将etl文件重命名为与PDB文件同名时,消息分析器解析WPP OK(有点慢,但没问题)
当我是尝试进行实时捕获(在注册提供者之后),跟踪是捕获,但未解析。
我几乎没有问题:
1。你有解决方案/根本原因吗?
2。是否有临时解决方案将捕获的文件保存为etl,并重新打开elt - 或类似的解决方案?
Message Analyzer 1.1已发布(请参阅博客
http: //blogs.technet.com/MessageAnalyzer )。我对WPP性能有一些改进。
对于实时捕获,我将不得不进行调查。 也许另一种解决方案是创建TMF,然后您可以设置一个消息分析器将搜索它们的目录。 如果您认为这可能对您有用,请告诉我。
我们无法保存为ETL,因为没有公共界面可以这样做。 当然我认为还有其他工具可以将数据捕获为ETL,如Logman。
谢谢,
Paul
Hi,
I'm using Message Analyzer 1.0.2 (The problem also exists in the official version).
When I capture WPP logs and rename the etl file to be as the same name as the PDB file, Message analyzer parses the WPP OK (a bit slow, but OK)
When I'm trying to do live capture (after registering the providers), the traces are captures, but not parsed.
I have few questions:
1. Do you have a solution/root cause for this?
2. Is there a temporary solution to save the captured file as an etl, and reopen the elt - or a similar solution?
Message Analyzer 1.1 has released (see the blog http://blogs.technet.com/MessageAnalyzer). I has some improvements we regards to WPP performance.
For a live capture, I'll have to investigate. Perhaps another solution is to create TMFs and then you can setup a directory where Message Analyzer will search for them. If you think this might work for you, let me know.
We can't save as ETL, as there's not a public interface to do that. Of course I think there are other tools to capture the data as an ETL, like Logman.
Thanks,
Paul
这篇关于Message Analyzer不解析WPP实时跟踪的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!