Skip to content
Tx (LINQ to Events)
C# Roff Other
Branch: master
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
Doc Update Nov 15, 2017
Generated Update Refresh script Oct 17, 2018
Manifests Renamed one of man file to manifest Oct 19, 2016
References Migrate to .NETCore2.0 Jul 24, 2018
Samples Get BondEtw Driver to build for new code base Mar 5, 2019
Source Publish Tx.Windows version 3.0.4 Apr 11, 2019
Test Migrate to .NETCore2.0 Jul 24, 2018
Tools Updates and improvements to BinaryParsers and IP to use MemoryStream … Nov 19, 2015
.gitignore Migrate to .NETCore2.0 Jul 24, 2018
Common.targets Migrate to .NETCore2.0 Jul 24, 2018
Contributors.txt Fixing links in the HTTP samples and adding Swetha to the contributors Oct 14, 2014
NuGet.Config Add NuGet.Config settings file Mar 5, 2019 Update Jun 1, 2017
TxCodeMap.JPG Small typos and markdown document root Mar 25, 2014

Nuget Build status

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:



  • 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


There are lots of ways to contribute to the project, and we appreciate our contributors. We strongly welcome and encourage contributions to this project. Please read the contributor's guide. If making a large change we request that you open an issue first. We follow the Git Flow approach to branching.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact with any additional questions or comments.

You can’t perform that action at this time.