Giter Club home page Giter Club logo

nlog.owin.logging's Introduction

NLog

NuGet Semantic Versioning NuGet downloads

Coverage

NLog is a free logging platform for .NET with rich log routing and management capabilities. It makes it easy to produce and manage high-quality logs for your application regardless of its size or complexity.

It can process diagnostic messages emitted from any .NET language, augment them with contextual information, format them according to your preference and send them to one or more targets such as file or database.

Major and minor releases will be posted on project news.

Getting started

For the possible options in the config, check the Options list and API Reference

Having troubles? Check the troubleshooting guide

ℹī¸ NLog 5.0 Released!

NLog 5.0 is finally here. See List of major changes in NLog 5.0

NLog Packages

The NLog-nuget-package provides everything needed for doing file- and console-logging. But there are also multiple NLog extension packages, that provides additional target- and layout-output. See targets and layout renderers overview!

See Nuget/build status of all official packages here

Questions, bug reports or feature requests?

Issues with getting it working? Please check the troubleshooting guide before asking! With a clear error message, it's really easier to solve the issue!

Unclear how to configure NLog correctly of other questions? Please post questions on StackOverflow.

Do you have feature request or would you like to report a bug? Please post them on the issue list and follow these guidelines.

Frequently Asked Questions (FAQ)

See FAQ on the Wiki

Contributing

As the current NLog team is a small team, we cannot fix every bug or implement every feature on our own. So contributions are really appreciated!

If you like to start with a small task, then up-for-grabs are nice to start with.

Please note, we have a dev and master branch

  • master is for pure bug fixes and targets NLog 4.x
  • dev targets NLog 5

A good way to get started (flow)

  1. Fork the NLog repos.
  2. Create a new branch in you current repos from the 'dev' branch. (critical bugfixes from 'master')
  3. 'Check out' the code with Git or GitHub Desktop
  4. Check contributing.md
  5. Push commits and create a Pull Request (PR) to NLog

Please note: bugfixes should target the master branch, others the dev branch (NLog 5)

License

NLog is open source software, licensed under the terms of BSD license. See LICENSE.txt for details.

How to build

Use Visual Studio 2019 and open the solution 'NLog.sln'.

For building in the cloud we use:

  • AppVeyor for Windows- and Linux-builds
  • SonarQube for code coverage

Trying to build your fork in the cloud? Check this how-to

Note: master points to NLog 4.x and dev to NLog 5.x

nlog.owin.logging's People

Contributors

304notmodified avatar alexdovgan avatar dependabot-support avatar pysco68 avatar snakefoot avatar

Stargazers

avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar

Watchers

avatar avatar avatar avatar avatar avatar avatar avatar

Forkers

kennylisc jango2015 alexdovgan snakefoot

nlog.owin.logging's Issues

"Incorrect" {callsite} value in log file

Today I used this library for the first time and I when I was reviewing the log files it generated, I found all calling methods to be "NLog.Owin.Logging.NLogFactory+Logger.WriteCore" instead of my class methods (using ${callsite}). Digging into the the code for NLog and this library I found out that NLog goes up the stack frame and finds the calling method, but since it does not "know" anything about your library, it assumes it is the correct one. (which is wrong in this case)

The problem gets solved by adding these 2 lines to my project, but I think it should be added to the library instead, so the end-user(developer) does not have to worry about it.

LogManager.AddHiddenAssembly(typeof(NLogFactory).Assembly);
LogManager.AddHiddenAssembly(typeof(LoggerExtensions).Assembly);

Hope it helps someone.

EventID is always 0

File: NlogAdapter
Method: WriteCore

Why I'm getting eventId = 0 when using WriteCore method?
You passing it into method as paramter, but never using it?

Thanks for response

Skip eventid-property when using default value zero

Should not insert EventId-property when eventid is not assigned (Has value zero).

NLog.Owin.Logging/NLog.Owin.Logging/NLogAdapter.cs

Line 110 in 71e739f

logEvent.Properties["EventId"] = eventId;

Also consider pre-boxing the common eventids 0-50 like this:

        private static readonly object[] EventIdBoxing = Enumerable.Range(0, 50).Select(v => (object)v).ToArray(); 

        private static object GetEventId(int eventId)
        {
            if (eventId >= 0 && eventId < EventIdBoxing.Length)
                return EventIdBoxing[eventId];
            else
                return eventId;
        }

EOL normalization

after .gitattributes has been changed:

rm .git/index     # Remove the index to force git to
git reset         # re-scan the working directory
git status        # Show files that will be normalized
git add -u
git commit -m "EOL normalization"

Add example of using Nlog adapter inside Controller

I've installed NLog.Owin.Logging package from Nuget, added app.UseNLog(); as first line in Configuration method in Startup class, I've setup everything inside NLog.config:

<?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"
      xsi:schemaLocation="http://www.nlog-project.org/schemas/NLog.xsd NLog.xsd"
      autoReload="true"
      throwExceptions="false"
      internalLogLevel="Off" internalLogFile="c:\temp\nlog-internal.log" >

  <targets>
    <target xsi:type="Database" name="Database" connectionStringName="ApplicationDbContext">
      <commandText>
        EXEC Add_Log @Data = @Date, @Rodzaj = @Level, @Wiadomosc = @Message;</commandText>
      <parameter name="@Message" layout="${message}"/>
      <parameter name="@Level" layout="${level:uppercase=true}"/>
      <parameter name="@Date" layout="${date}"/>
    </target>
  </targets>

  <rules>
    <logger name="*" minlevel="Trace" writeTo="Database" />
  </rules>
</nlog>

but my log table is empty. I've checked SQL Server Profiler and I don't see my procedure being called.
I'm using standard:

var logger = LogManager.GetCurrentClassLogger();
logger.Error("Error");

What I would like to request is simple example of how to setup and use NLog.Owin.Logging with Owin ASP site.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤ī¸ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.