Tx (LINQ to Events)
Перейти к файлу
georgis dac6098129 Markdown doc for the IIS samples 2014-03-22 19:36:15 -07:00
Doc Adding documentation root for git/markdown 2014-03-22 18:20:12 -07: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 Rx to 2.2.2 2014-01-23 17:38:36 -08:00
Samples Markdown doc for the IIS samples 2014-03-22 19:36:15 -07:00
Source Readme.md for the LINQPad driver 2014-03-22 18:46:12 -07:00
Test Removing the testcase that needed giant file (AspTrace.etl) 2014-01-07 14:45:54 -08: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
README.md Basic (demo quality) support for XEvent in LINQPad 2013-06-22 16:25:45 -07:00
license.txt

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