BizTalk 检测和 ETW 事件负载
我正在使用 BizTalk Instrumentation 最佳实践，将自定义跟踪添加到现有的 BizTalk 组件 ETW 提供程序中。我还使用 BizTalk CAT Instrumentation Framework Controller 来管理我的 ETW 跟踪并将其记录到 ETL 二进制文件中。生成跟踪后，“tracefmt.exe”工具与框架提供的“Default.tmf”事件定义文件一起帮助生成包含日志的简单文本文件，例如：
011BC.15A4::11:08:46.139 Event:TRACEIN: Microsoft(…).segment1("Orchestration start.") => 82ed2e95-130a-4f28-8fd8-e921b6ef9c40
11BC.15A4::11:08:46.139 [Event]:INFO: Some useful information logged here
11BC.15A4::11:08:46.139 [Event]:TRACEOUT: Microsoft(...).segment1("Orchestration end.") = <void> <= [82ed2e95-130a-4f28-8fd8-e921b6ef9c40]
这一切都非常有用，但信息量似乎很大实际上存储在 ETW 中的事件是有限的。因此，我有几个问题需要进一步推动日志和框架的可用性：
- 日志和生成的文本文件包含 (1) 时间戳和 (2) 消息文本。记录的 ETW 事件中是否有更多实际可用的信息？例如，事件级别整数（信息、警告、错误等）实际上记录在 ETL 中还是仅记录在消息中？
- 为了跟进上一个问题，是否有一个更完整的“TMF”文件可以通过 ETW 事件公开 ETL 中的额外信息存储？
- 是否可以将 ActivityId 等信息添加到通过框架记录到 ETW 的事件中？
非常感谢！
I am using the BizTalk Instrumentation Best Practices to add custom traces to the already available BizTalk components ETW providers. I also use the BizTalk CAT Instrumentation Framework Controller to manage my ETW traces and log them to an ETL binary file. Once traces are produce, the "tracefmt.exe" tool together with the "Default.tmf" event definition file provided with the framework help produce simple text files containing logs such as:
011BC.15A4::11:08:46.139 Event:TRACEIN: Microsoft(…).segment1("Orchestration start.") => 82ed2e95-130a-4f28-8fd8-e921b6ef9c40
11BC.15A4::11:08:46.139 [Event]:INFO: Some useful information logged here
11BC.15A4::11:08:46.139 [Event]:TRACEOUT: Microsoft(...).segment1("Orchestration end.") = <void> <= [82ed2e95-130a-4f28-8fd8-e921b6ef9c40]
This is all very useful, but it seems the amount of information actually stored in the ETW events is limited. I therefore have a few questions to push the usability of the logs and framework further:
- The logs and the generated text file contain (1) a timestamp and (2) the text of the message. Is there more information actually available in the logged ETW event? For example, is the event level integer (Info, Warning, Error, etc...) actually logged in the ETL or just the message?
- To follow-up on the previous question, is there a more complete "TMF" file that would expose the extra information store in the ETL with the ETW events?
- Is it possible to add information such as the ActivityId to the events logged to ETW through the framework?
Many thanks!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
如果您有兴趣，请查看我在 MS BizTalk 论坛上收到的答案：
http://social.msdn.microsoft.com/Forums/en-US/biztalkgeneral/thread/17c20386-c550-4412-93d7-930a1b9679c8
简短的结论：CAT 最佳实践可以是对于通过内置 BizTalk Server ETW 通道进行登录的快速解决方案很有用，但在自定义方面提供的很少。
If you are interested, please have a look at the answer I have received on a MS BizTalk forum:
http://social.msdn.microsoft.com/Forums/en-US/biztalkgeneral/thread/17c20386-c550-4412-93d7-930a1b9679c8
Short conclusion: the CAT best practices can be useful for a quick solution to log through the built-in BizTalk Server ETW channels, but offers little in terms of customization.