cdmdotnet.Logging 1.2.95.72

Prefix Reserved
There is a newer version of this package available.
See the version list below for details.
dotnet add package cdmdotnet.Logging --version 1.2.95.72                
NuGet\Install-Package cdmdotnet.Logging -Version 1.2.95.72                
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="cdmdotnet.Logging" Version="1.2.95.72" />                
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add cdmdotnet.Logging --version 1.2.95.72                
#r "nuget: cdmdotnet.Logging, 1.2.95.72"                
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install cdmdotnet.Logging as a Cake Addin
#addin nuget:?package=cdmdotnet.Logging&version=1.2.95.72

// Install cdmdotnet.Logging as a Cake Tool
#tool nuget:?package=cdmdotnet.Logging&version=1.2.95.72                

This logging library makes large use of enterprise correlation.
In a lot of applications that incorporate various small and large services, it is often important to correlate events that happen across these services. It gives us a business workflow view of the various events that happen in the application, its components and services.
This library provide operation and activity ID management and propagation.

The main difference with this library over other is that you can configure each type of log separately. You can enable fatal, error, warning, debugging, informational, progress and sensitive data logging all independently of each other.
This is more flexible than the concept of minimum level logging, such as that in log4net or serilog e.g. enabling one warning in this libraries will enable error and fatal logging as well. This library allows you to set those settings independently of each other.

The SqlLogger maps AdditionalData to table columns, where the key of the dictionary entry is the column name and the value is serialised to JSON as the column value.
MetaData is serialised to a single JSON value stored in the MetaData column.
This means you can store data such as a User ID or Job ID in a separate column so you can filter more efficiently with indexes and partitions.

TraceLogger and ConsoleLogger both seralise and format all information into a single string.
The MultiLogger allows you to configure several different loggers to be used at once with different settings for each logger.

Usage is in the form of:
static void Main()
{
  ICorrelationIdHelper correlationIdHelper = new WebCorrelationIdHelper();
  // This value will be set automatically to all logs within this thread... so long as System.Threading.Tasks.Task.Factory.StartNew is used.
  correlationIdHelper.SetCorrelationId(Guid.NewGuid());
  DoSyncWork();
  DoAsyncWork();
}

static void DoSyncWork()
{
  ILogger logger = new SqlLogger();
  logger.LogDebug("Some technical debugging details.");
}

static void DoAsyncWork()
{
  System.Threading.Tasks.Task.Factory.StartNew(() => {
    ILogger logger = new ConsoleLogger();
    logger.LogInfo("An informative message.");
  });
}

This package installs cdmdotnet.Logging.dll with includes core logging functionality. Other packages depend on cdmdotnet.Logging for specific implementations.

Product Compatible and additional computed target framework versions.
.NET Framework net40 is compatible.  net403 was computed.  net45 was computed.  net451 was computed.  net452 was computed.  net46 was computed.  net461 was computed.  net462 was computed.  net463 was computed.  net47 was computed.  net471 was computed.  net472 was computed.  net48 was computed.  net481 was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (13)

Showing the top 5 NuGet packages that depend on cdmdotnet.Logging:

Package Downloads
Cqrs.Mongo

Use MongoDB as the read store and data store in CQRS.NET

Cqrs.Azure.DocumentDb

Use Azure Cosmos DB (DocumentDB) as an event store, read store and data store in CQRS.NET

Cqrs.Ninject.Azure.DocumentDb

Use Ninject as your IoC container of choice with Microsoft Azure DocumentDB for CQRS.NET

Cqrs.Sql

The built-in, Sql Store in the CQRS.NET cannot process non-primitive properties on the entity classes in read stores and data stores. If your entity classes require more comp[lexity than just basic, flat primitive property structures, this package will allow you to use Microsoft SqlServer as an read store and data store in CQRS.NET allowing you to build custom converters to provide mappings from your entities to you SQL table schema structures.

Cqrs.Akka

Use Akka.NET actors in CQRS.NET

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
1.2.104.81 3,840 6/17/2018
1.2.103.80 2,441 6/17/2018
1.2.102.79 2,454 6/4/2018
1.2.101.78 2,421 6/4/2018
1.2.100.77 36,033 5/11/2018
1.2.99.76 2,446 5/11/2018
1.2.97.74 2,627 4/19/2018
1.2.96.73 2,674 3/29/2018
1.2.95.72 61,855 8/22/2017
1.2.91.71 74,698 5/30/2017
1.2.89.69 2,436 5/3/2017
1.2.87.68 9,728 4/18/2017
1.2.84.66 2,544 3/21/2017
1.2.80.64 2,448 3/21/2017
1.2.78.63 2,529 3/21/2017
1.2.77.62 2,537 3/19/2017
1.2.74.61 2,358 3/19/2017
1.2.71.60 2,470 3/14/2017
1.2.69.59 2,564 3/13/2017
1.2.66.58 2,383 3/7/2017
1.2.65.57 2,293 3/7/2017
1.2.64.56 2,257 3/6/2017
1.2.58.50 2,345 2/20/2017
1.2.55.48 2,159 2/14/2017
1.2.54.47 2,175 2/8/2017
1.2.53.46 2,087 1/23/2017
1.2.51.44 3,941 12/2/2016
1.2.50.43 2,194 12/2/2016
1.1.49.42 2,166 12/2/2016
1.1.48.41 2,123 12/2/2016
1.1.46.40 2,259 12/2/2016
1.1.45.39 3,432 12/2/2016
1.1.43.36 2,412 12/2/2016
1.1.43.31 2,433 11/28/2016
1.1.42.30 3,034 11/23/2016
1.1.40.29 2,258 11/22/2016
1.1.39.28 2,384 11/17/2016
1.1.37.27 3,085 11/1/2016
1.1.36.26 10,574 10/18/2016
1.1.35.25 2,653 5/23/2016
1.1.34.24 2,470 5/22/2016
1.1.32.23 2,383 5/20/2016
1.1.31.22 2,431 5/18/2016
1.1.30.21 1,959 5/16/2016
1.1.27.20 1,960 5/16/2016
1.0.24.24 250,027 9/23/2015
1.0.23.23 7,142 9/23/2015
1.0.20.21 82,916 9/9/2015
1.0.19.20 2,047 9/9/2015
1.0.18.19 1,967 9/9/2015
1.0.17.19 2,043 9/9/2015
1.0.16.18 1,992 9/9/2015
1.0.15.17 2,081 9/9/2015
1.0.14.16 1,991 9/9/2015
1.0.13.14 24,655 9/2/2015
1.0.12.13 2,075 9/2/2015
1.0.11.12 43,422 8/26/2015
1.0.10.11 11,327 8/26/2015
1.0.9.10 2,064 8/26/2015
1.0.7.9 66,587 5/27/2015
1.0.6.8 2,468 5/27/2015

Version 1.2.93

* Replaced a few usages of collections with better thread safe collections for much higher usage environments.

Version 1.2.92

* Added a null reference check to the configuration file base settings class to return a better error if there is an issue.

Version 1.2.91

* Added better support for serialisation issue with exceptions and meta-data - which are both considered secondary to trying to save all other information.

Version 1.2.88

* Added a sample SQL script for creating the logs table, see the tools folder.

Version 1.2.87

* Added the ability to turn off using performance counters. You may need to add a new property to your app.config or web.config "UsePerformanceCounters" with a boolean value.

Version 1.2.77

* Added optional properties to all telemetry methods.

Version 1.2.74

* Added Telemetry.

Version 1.2.65

* Refactored all loggers to use a simplified classes for more consistency.

Version 1.2.60

* Added MultiLogger.

Version 1.2.58

* Added the ability to specify the table to be used in the data so you can separate systems into different tables but have them all in the same DB
* Fixed poor handling of a missing connection string configuration.

Version 1.2.52

* Switched to using (and referencing) cdmdotnet.Statemanagement for controlling the passing of the CorrelationId from thread to thread safely when using Parallel Tasks.

Version 1.2.51

* Added Logger settings as a better default when using app.config and web.config files.

Version 1.1.49

* Replaced the threaded model with Parallel Tasks.

Version 1.1.48

* Resolved an issue where a NullReferenceException if AdditionalData was null.
* Added some documentation to explain how MetaData and AdditionalData is stored.

Version 1.1.46

* Remove cdmdotnet.Logging.Sql

Version 1.1.45

* Resolved an issue where a NullReferenceException could be raised during logging.
* Merged SqlLogger into cdmdotnet.Logging.

Version 1.1.39

* Added MetaData property
* Added AdditionalData property