Effective, Real World, Logging in .NET Core Applications
.NET and C#
Starting with blank .NET Core templates they make logging seem simple, however, look deeper and you will find that many key features are lacking. True configuration ability, remote logging, SQL Logging, Email Alerts, and more. Let us explore how to make logging work for you!
Anyone can setup a new .NET Core application and have basic log information written to the console. This is fantastic when working with a quick prototype application, but how do you manage the real-world situations? How do you configure logging in different environments, with alert levels appropriate for your particular environment How about integrating logging into your support system or other critical alerting? It seems simple, however, I find that many people get bogged down with the details of implementation and often gloss over.
This session will explore strategies to implement logging with full ability to Unit Test what is happening while supporting the utmost flexibility in logging using the Seilog framework. In this deep dive session we will review configuration highlights including.
<li>Including or Excluding Microsoft Logging Details</li>
<li>Logging EF query performance</li>
<li>Working with startup exceptions</li>
<li>Methods to escalate errors via channels such as EMail and otherwise</li>
<li>Avoiding duplication of configuration from project-to-project</li>
Attendees will be able to download a sample application with all of the examples and documentation after the session.