.NET EventSource活动跟踪规范
52 浏览量
更新于2024-07-14
收藏 451KB PDF 举报
"EventSource Activities Specification 是微软发布的一份关于EventSource活动支持的详细技术文档，主要关注在.NET环境中如何高效地进行日志记录，并在并发和异步场景下通过关联ID来追踪和分组事件。这份文档适用于服务器应用程序开发，旨在解决在历史编程实践中由于手动处理关联ID而导致的复杂性、不一致性以及常见错误。文档完整度为完成状态，最后更新于2019年3月13日。"
本文档主要讨论了以下知识点：
1. **EventSource**：
EventSource是.NET框架中的一个高性能日志记录工具。它能够帮助开发者快速记录应用程序中的关键事件，尤其是在并发和异步操作的服务器应用环境中，这对于跟踪和分析系统行为至关重要。
2. **活动（Activity）追踪**：
在并发和异步场景下，服务器应用程序需要能够将事件与关联ID（correlation ID）标记，以便根据更高级别的概念，如请求、会话或用户，来组合和过滤事件。这有助于理解事件之间的因果关系和流程。
3. **问题与挑战**：
在过去，关联ID的生成和传递通常需要程序员显式处理，导致代码复杂、设计不一致，而且容易重复出现错误。这是许多开发者面临的一个常见难题。
4. **解决方案**：
在.NET运行时的4.6版本中，EventSource引入了一种新的机制，几乎自动化了通用关联ID的生成和传播工作，使得将因果相关的事件与如请求等高层构造关联变得非常简单。
5. **使用EventSource活动支持**：
文档的第二部分介绍了如何利用EventSource活动支持功能，包括最终用户体验、API用法、最佳实践等内容，帮助开发者更有效地在他们的应用程序中集成和使用活动追踪。
6. **内容结构**：
文档包括了引言，详细解释了为什么需要活动追踪，以及如何使用EventSource的活动支持功能。此外，还有可能包括具体的步骤指南、示例代码和可能的故障排查内容。
通过学习和应用这份规范，开发者可以提升.NET应用程序的日志记录质量，更好地理解和诊断系统中的问题，提高服务器应用的性能和可维护性。
Page 3
Microsoft Confidential. © 2019 Microsoft Corporation. All rights reserved. By using or providing feedback on these materials, you agree to the attached license agreement.
Cross event correlation is indispensable in a server environment.
2. Using EventSource Activity Support
In a later section, we will talk about some of the alternatives to the approach that EventSource took to provide
event correlation, however, rather than start out with the ‘bad’ ideas, we start with presenting the ‘good’ one,
which EventSource adopted.
2.1 End User Experience
From an end user experience point of view, to a very good approximation, EventSource activity support is an ‘it
just works’ feature. In particular the EventSource scenario described in section 1 DOES NOT CHANGE AT ALL,
and yet, now when processing the event data, you now have acesss to an ‘ActivityID’ that allows you to
correlate events in the way you wish to. For example, if you ran the application on Version 4.6 of the .NET
runtime, and used version V1.8 of PerfView or higher to collect and view the EventSource data, you would get a
view of events that would look like this.
Event Name
TimeStamp
ThreadID
ActivityID
DURATION_MSEC
MyCompany-MyService/Request/Start
6,619.23
3,576
//1/1/6/1
MyCompany-MyService/Security/Start
9,403.14
6,228
//1/1/6/1/1/2
MyCompany-MyService/Security/Stop
9,723.26
6,228
//1/1/6/1/1/2
320.112
MyCompany-MyService/DatabaseCommand/Start
12,214.79
4,508
//1/1/6/1/2
MyCompany-MyService/DatabaseCommand/Stop
12,215.13
4,508
//1/1/6/1/2
0.341
MyCompany-MyService/DatabaseCommand/Start
13,085.57
8,916
//1/1/6/1/3/1
MyCompany-MyService/DatabaseCommand/Stop
13,085.68
8,916
//1/1/6/1/3/1
0.106
MyCompany-MyService/Security/Start
13,085.79
8,916
//1/1/6/1/3/2
MyCompany-MyService/Security/Stop
13,394.61
8,916
//1/1/6/1/3/2
308.821
MyCompany-MyService/Request/Stop
15,385.33
8,196
//1/1/6/1
8,766.093
The new information in V4.6 is the ‘ActivityID’ and DURATION_MSEC in the output above. The first thing you
notice is that the ActivityID is not a ‘flat’ number but something that looks much more like a path (e.g
//1/1/6/1). This is because each activity has a ‘parent’ that ‘caused’ it, and these causal relationships
naturally form tree, and the natural ID for a node in the tree is the path from the root of the tree to a node.
These causal relationships also correspond to nesting relationships among the activities. Thus we see that the
‘Security’ activity (with Id //1/1/6/1/1/2) must be ‘caused’ (part of or nested inside) the ‘Request’ activity (with
Id //1/1/6/1) because //1/1/6/1 is a prefix of //1/1/6/1/1/2.
For example, filtering so that you only see ALL events associated with a particular request (e.g. like //1/1/6/1) is
as simple pattern matching on the //1/1/6/1 prefix. In fact the trace that the data above came from had 8
concurrent requests, but we could easily filter to see just one of them by this simple prefix test.
Once all events have such an ID, it is a simple matter to compute durations by subtracting the timestamp for the
start from the timestamp for the stop. This is what the DURATION_MSEC column is.
剩余19页未读，继续阅读
2019-09-03 上传
2021-04-22 上传
2021-04-22 上传
2021-04-22 上传
2021-05-03 上传
2024-06-11 上传
2021-04-22 上传
2021-04-22 上传
weixin_38576229
- 粉丝: 5
- 资源: 901
我的内容管理
展开
最新资源
- AA4MM开源软件：多建模与模拟耦合工具介绍
- Swagger实时生成器的探索与应用
- Swagger UI：Trunkit API 文档生成与交互指南
- 粉红色留言表单网页模板，简洁美观的HTML模板下载
- OWIN中间件集成BioID OAuth 2.0客户端指南
- 响应式黑色博客CSS模板及前端源码介绍
- Eclipse下使用AVR Dragon调试Arduino Uno ATmega328P项目
- UrlPerf-开源：简明性能测试器
- ConEmuPack 190623：Windows下的Linux Terminator式分屏工具
- 安卓系统工具：易语言开发的卸载预装软件工具更新
- Node.js 示例库：概念证明、测试与演示
- Wi-Fi红外发射器：NodeMCU版Alexa控制与实时反馈
- 易语言实现高效大文件字符串替换方法
- MATLAB光学仿真分析：波的干涉现象深入研究
- stdError中间件：简化服务器错误处理的工具
- Ruby环境下的Dynamiq客户端使用指南
