Found 63 packages
Provides classes that help you trace the execution of your code. Developers should prefer the classes in the ETW-based System.Diagnostics.Tracing package. Commonly Used Types: System.Diagnostics.TraceListener System.Diagnostics.TraceLevel System.Diagnostics.TraceSource System.Diagnostics.TraceEventType System.Diagnostics.DefaultTraceListener System.Diagnostics.Trace When using NuGet 3.x this package requires at least version 3.4.
TraceSource logger provider implementation for Microsoft.Extensions.Logging. This logger logs messages to a trace listener by writing messages with System.Diagnostics.TraceSource.TraceEvent().
Event Tracing for Windows (ETW) is a powerful logging mechanism built into the Windows OS and is used extensively in Windows. You can also log ETW events yourself code using the System.Diagnostics.Tracing.EventSource class. The TraceEvent library conains the classes needed to control ETW providers (including .NET EventSources) and parse the events they emit. The library includes -- TraceEventSession which can enable ETW providers, -- EtwTraceEventSource which lets you read the stream of ETW events, and -- TraceLog which is is digested form of ETW events which include decoded stack traces associated with the events. See https://github.com/Microsoft/perfview/blob/master/documentation/TraceEvent/TraceEventLibrary.md for more.
Makes configuring tracing easy and standardized for .NET Core, .NET Standard, and .NET Framework.
Full information stack trace without deploying PDBs Don't want to deploy PDBs, but still get exception stack traces that map to original source line numbers? Want to have your cake and eat it too? ProductionStackTrace is intended to run in Production, without any access to PDB symbol files. It produces a stack trace with enough information to be analyzed by the techies back on the base with a help of a Symbol Store to get original source code line numbers. Usage & documentation is at: https://github.com/gimelfarb/ProductionStackTrace
NLog Integration for Microsoft System.Diagnostics.DiagnosticSource and Activity TraceId / SpanId
PostSharp.Patterns.Diagnostics: support for Trace, TraceSource and EventSource.
Parser for .NET and Mono stack traces.
Micro-framework for logging with the .NET TraceSource API
Formatter for .NET and Mono stack traces.
This is not the recommended package for working with Cloudtrace, please use the Google.Cloud.Trace.V1 package. This Google APIs Client Library for working with Cloudtrace v1 uses older code generation, and is harder to use. Product documentation is available at: https://cloud.google.com/trace/ API reference documentation for this package is available at: https://googleapis.dev/dotnet/Google.Apis.CloudTrace.v1/latest/api/Google.Apis.CloudTrace.v1.html The source code for this package is available at: https://github.com/google/google-api-dotnet-client/tree/master/Src/Generated/Google.Apis.CloudTrace.v1 Supported Platforms: - .NET Framework 4.6.2+ - .NET Standard 2.0 - .NET 6.0+ Incompatible platforms: - .NET Framework < 4.6.2 - Silverlight - UWP (will build, but is known not to work at runtime) - Xamarin/MAUI - Windows 8 Apps - Windows Phone 8.1 - Windows Phone Silverlight 8.0
A sample of how to consume ETW event from C#. The NuGet package contains the source code.
Logging implementation of Rsft.Lib.Patterns.Logging for enterprise systems. Uses System.Diagnostics.TraceSource under the hood.
Automatically implements the tedious part of the .NET EventSource classes. Also automatically converts any interface to an ETW trace point. Wrap your interfaces and get free ETW tracing. ** Now with .NET Standard 2.0 support! **
Contains TraceSourceAttribute - a PostSharp-based aspect for simple but rich logging with .Net System.Diagnostics framework. It makes completely simple to use activity tracing and locial operations stacks.
This is not the recommended package for working with Cloudtrace, please use the Google.Cloud.Trace.V2 package. This Google APIs Client Library for working with Cloudtrace v2 uses older code generation, and is harder to use. Product documentation is available at: https://cloud.google.com/trace/ API reference documentation for this package is available at: https://googleapis.dev/dotnet/Google.Apis.CloudTrace.v2/latest/api/Google.Apis.CloudTrace.v2.html The source code for this package is available at: https://github.com/google/google-api-dotnet-client/tree/master/Src/Generated/Google.Apis.CloudTrace.v2 Supported Platforms: - .NET Framework 4.6.2+ - .NET Standard 2.0 - .NET 6.0+ Incompatible platforms: - .NET Framework < 4.6.2 - Silverlight - UWP (will build, but is known not to work at runtime) - Xamarin/MAUI - Windows 8 Apps - Windows Phone 8.1 - Windows Phone Silverlight 8.0
Email trace listener extension for System.Diagnostics, along with required config sections. Sends each trace message received in an email, using the specified subject and body templates. Note: Set a filter to avoid flooding (don't rely on trace source switch value). Other Essential.Diagnostics packages extend the .NET Framework System.Diagnostics trace logging with additional trace listeners. Included are colored console (that allows custom formats), SQL database (including a tool to create tables), rolling file (with custom formats), rolling XML, email (per trace or batched), and an in-memory trace listener. The Essential.Diagnostics project also publishes a fluent client library that includes easy encapsulation of activity and logical operation scopes, as well as abstractions and templated classes for a simpler logging API and support for dependency injection frameworks. See the project site on CodePlex for examples and documentation.
This package contains the logging libaray built around Microsofts Trace Source libaray.
Yaaf.Logging is a simple abstraction layer over a logging library (designed for System.Diagnostic.TraceSource).
JsTrace allows you to heavily instrument your JavaScript code without flooding the console with messages. It has "Trace Levels" (off, error, warn, info, debug, log), which allow you to fine-tune what amount of trace information comes out of each area or module of your code. It additionally supports a callback function to allow further processing of Trace messages. It is cross-browser and will gracefully degrade down to "console.log" on browsers without support for higher level methods like console.error.