Tx (LINQ to Events)
Перейти к файлу
georgis 5092f7612e Changing the packages to "LINQ to Logs and Traces" 2013-12-28 10:47:24 -08:00
Doc Trying absolute hyperink for JPG refered from markdown 2013-12-23 00:05:01 -08:00
Generated (jomorri) Task enumeration as EventTask Enum 2013-05-28 20:23:32 -07:00
Manifests Adding two machine LINQPad sample (Internet Explorer and IIS) 2013-05-21 00:01:07 -07:00
References Update the LINQPad driver 2013-10-25 20:49:47 -07:00
Samples Try link from .md file to code 2013-09-02 13:44:11 -07:00
Source Changing the packages to "LINQ to Logs and Traces" 2013-12-28 10:47:24 -08:00
Test Step one of parsing W3C logs from IIS 2013-06-09 23:17:10 -07:00
Tools Script to push NuGet packages 2013-03-13 09:39:54 -07:00
Traces Basic (demo quality) support for XEvent in LINQPad 2013-06-22 16:25:45 -07:00
.gitignore Performance fixes and tests for synthetic counters 2013-03-12 13:05:48 -07:00
Common.targets Perf counter fix and warning cleanup 2013-02-26 20:40:43 -08:00
README.md Basic (demo quality) support for XEvent in LINQPad 2013-06-22 16:25:45 -07:00
license.txt Move Tx out of Rx repo. 2012-12-21 14:09:28 -08:00

README.md

Tx (LINQ to Logs and Traces)

Tx is set of code samples showing how to use LINQ to events, such as:

  • Real-Time standing queries:. E.g. producing a histogram every second how many bytes were send/received over TCP per IP address.
  • Queries on past history from trace/log files: E.g. from past trace of IIS find the slow requests by correlating "begin" and "end" events.

The initial set of supported technologies is:

  • Event Tracing for Windows (ETW)
  • Windows Event Logs
  • W3C Logs from IIS
  • Performance counter captures (.blg, ,csv, .tsv)
  • SQL Server Extended Events (XEvent)

At its very core the Tx approach represents design pattern for building parsers. I.e. extending it is easy.

Example of the extensibility is trace in the ULS (Unified Logging Service) format