Integrating Logging Using NLog in ASP.NET Core Web App

NLog: It is an open resource logging structure that provides a great versatility as well as configurable alternatives to log the understandings of your application. It permits to choose several targets like database, cloud solutions, files, console, and so on at the same time to make sure that customer do not need to keep various arrangements in code. This is the most extensively made use of logging structure available.

Several of the vital features are:

• It’s very easy to configure
• It is based on themes
• It has actually pre-defined formats to ensure that you can change messages with custom data
• It provides structured logging

Official website of open source job: https://nlog-project.org/ Creating ASP.NET Core job

1. 1. 1. 1. Open Visual Workshop 2019 and also produce a brand-new project.
         2. Select ASP.NET Core Web Application from project templates
         3. Choose the name of the project and click Create button.
         4. Select Web Application Template and make appropriate selections

         5. The above 4 steps will create an ASP.NET Core 3 Web Application with some default documents as well as folders. As we need to incorporate NLog in the application, we require to set up some bundles from NuGet plan supervisor.

            1. NLog.Web.AspNetCore— This is the plan that will set up NLog packages.

            2. NLog.config— This package will add a config file where we can define all the guidelines and targets for NLog arrangement. NLog collections will certainly check out all setup from this file.

         6. Once we include the needed plans, allows develop a configuration in NLog.config where we will certainly define a target which will certainly create logs to a data on our local system.

            Change the immediately produced code with the below code in NLog.config file.

      <?xml version="1.0" encoding="utf-8" ?>
      <nlog xmlns="http://www.nlog-project.org/schemas/NLog.xsd"
            xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
            autoReload="true"
            throwExceptions="false"
            internalLogLevel="Off" internalLogFile="c:\temp\nlog-internal.log">
       
        <targets>
          <target xsi:type="File" name="fileTarget" filename="..\logs\log.txt"></target>
        </targets>
       
        <rules>
          <logger name="*" minlevel="Trace" writeTo="fileTarget" />
        </rules>
      </nlog>

We likewise require to make change to the residential or commercial property of this data to ensure that this file can be replicated to directory site at the time of application deployment. Right click NLog.config file and pick residential properties option and please make the adjustments as shown listed below.

 7.  Once we add the target to submit in config documents, we need to sign up NLog as a service in Program.cs documents to ensure that I can catch logs as well as send them to the defined target.

Change the code in Program.cs data with the below highlighted.

public static IHostBuilder CreateHostBuilder(string[] args) =>
            Host.CreateDefaultBuilder(args)
                .ConfigureLogging((hostingContext, logging) =>
                {
                    logging.AddConfiguration(hostingContext.Configuration.GetSection("Logging"));
                    logging.AddDebug();
                    logging.AddNLog();
                })
                .ConfigureWebHostDefaults(webBuilder =>
                {
                    webBuilder.UseStartup<Startup>();
                });

At the time of WebHost production, we are infusing logging before calling Startup.cs file. ConfigureLogging approach highlighted over is adding logs to two services.

One is Debug home windows which is an attribute of Visual Workshop as well as Other one is NLog. AddNLog method belongs of Nuget plan that we set up in above steps.

AddConfiguration approach is trying to review logging configuration which is by default produced by Asp.Net Core job design template.

We can additionally specify NLog as service in Startup.cs class. The reason behind calling this prior to startup course is that occasionally there are some runtime problems that can be triggered before Start-up class is called, so we will be able to capture them also.

8. Now run the application and you will find that a log file is created in bin folder of your project.

Keep in mind: You can define any kind of path in the data name building in NLog.config and also this will certainly develop a log documents there. There are a lot of customizations that you can do in NLog config documents. Have a look at them at the asp.net mvc growth main web site mentioned in the beginning section of this post.