Tx (LINQ to Events)
Перейти к файлу
Jose Morris 2720d64450 Migrate to .NETCore2.0 2018-07-24 08:28:41 -07:00
Doc Update WhenToUse.md 2017-11-15 10:11:16 -08:00
Generated Fix in the Performance Baseline csv format 2014-10-06 20:56:43 -07:00
Manifests Renamed one of man file to manifest 2016-10-19 13:56:17 -07:00
References Migrate to .NETCore2.0 2018-07-24 08:28:41 -07:00
Samples Migrate to .NETCore2.0 2018-07-24 08:28:41 -07:00
Source Migrate to .NETCore2.0 2018-07-24 08:28:41 -07:00
Test Migrate to .NETCore2.0 2018-07-24 08:28:41 -07:00
Tools Updates and improvements to BinaryParsers and IP to use MemoryStream and BinaryReaders. 2015-11-19 15:42:20 -08:00
Traces Sample for Tx.Network, and SNMP parsing first draft 2015-12-02 01:37:52 -08:00
.gitignore Migrate to .NETCore2.0 2018-07-24 08:28:41 -07:00
Common.targets Migrate to .NETCore2.0 2018-07-24 08:28:41 -07:00
Contributors.txt Fixing links in the HTTP samples and adding Swetha to the contributors 2014-10-13 18:17:24 -07:00
README.md Update README.md 2017-06-01 13:48:14 -07:00
TxCodeMap.JPG
license.txt Updated the license text 2017-06-17 11:21:16 -07:00

README.md

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:

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

Contributing

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 opencode@microsoft.com with any additional questions or comments.