Tx (LINQ to Events)
Перейти к файлу
Sergey Baranchenkov 6149c056ff Fixed bug with incorrect FILETIME conversion to DateTime for ETW and Performance Counter sources 2015-09-30 20:47:27 -07:00
Doc .Net tracing API doc cleanup 2015-09-09 15:50:23 -07:00
Generated Fix in the Performance Baseline csv format 2014-10-06 20:56:43 -07:00
Manifests Added WCF sample trace and manifest to samples. 2014-10-03 14:37:40 -07:00
References Addded missing files 2015-06-26 11:01:04 -07:00
Samples Doc for Bond-ETW (and other serialization formats) root level sample 2015-08-30 14:09:40 -07:00
Source Fixed bug with incorrect FILETIME conversion to DateTime for ETW and Performance Counter sources 2015-09-30 20:47:27 -07:00
Test Fixed bug with incorrect FILETIME conversion to DateTime for ETW and Performance Counter sources 2015-09-30 20:47:27 -07:00
Tools Script to push NuGet packages 2013-03-13 09:39:54 -07:00
Traces Sample Bond-ETW self-contained file and version update 2015-08-25 17:21:08 -07:00
.gitignore
Common.targets
Contributors.txt Fixing links in the HTTP samples and adding Swetha to the contributors 2014-10-13 18:17:24 -07:00
README.md typos in the root README.md 2014-03-24 19:54:07 -07:00
TxCodeMap.JPG Small typos and markdown document root 2014-03-24 19:32:35 -07:00
license.txt

README.md

Tx (LINQ to Logs and Traces)

Tx allows you to do Language Integrated Query (LINQ) directly on raw event sources:

  • ad-hoc query on past history in trace and log files
  • standing queries on real-time feeds, such as Event Tracing for Windows (ETW) sessions

The Tx approach is different than Databases, Hadoop, Splunk, Dapper, etc. which all require a stage of uploading before the events become available to queries.

Instead, mixing Reactive Extensions (Rx) and LINQ-to-Objects allows the query to be embedded anywhere including:

The following picture shows the dependencies among the main Tx components:

TxCodeMap.JPG

Here:

  • Dark green is .Net
  • Light green is mature open source
  • Light grey are framework components, also available on NuGet
  • Darker gray are tool experiences that come with Tx
  • White are samples

For more see the documentation

Contribute

There are lots of ways to contribute to the project, and we appreciate our contributors.

You can contribute by reviewing and sending feedback on code checkins, suggesting and trying out new features as they are implemented, submit bugs and help us verify fixes as they are checked in, as well as submit code fixes or code contributions of your own. Note that all code submissions will be rigorously reviewed and tested by the Rx Team, and only those that meet an extremely high bar for both quality and design/roadmap appropriateness will be merged into the source.

You will need to sign a Contributor License Agreement before submitting your pull request. To complete the Contributor License Agreement (CLA), you will need to submit a request via the form (select "Reactive Extensions") and then electronically sign the Contributor License Agreement when you receive the email containing the link to the document. This needs to only be done once for any Microsoft Open Technologies OSS project.