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.
For the possible options in the config, check the Options list
Having troubles? Check the troubleshooting guide
NLog 4.5 implements the platforms added in NLog 5 (.NET Standard 1, .NET Standard 2, UWP, etc) and added structural logging, without breaking changes!
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.
Frequently Asked Questions (FAQ)
See FAQ on the Wiki
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.
A good way to get started (flow)
- Fork the NLog repos.
- Create a new branch in you current repos from the 'dev' branch. (critical bugfixes from 'master')
- 'Check out' the code with Git or GitHub Desktop
- Check contributing.md
- Push commits and create a Pull Request (PR) to NLog
NLog is open source software, licensed under the terms of BSD license. See LICENSE.txt for details.
How to build
Use Visual Studio 2017 and open the solution 'NLog.sln' - C# 7.2 support is required.
For building in the cloud we use:
- AppVeyor for Windows builds, including Silverlight and Xamarin.
- Travis for Mono builds.
- CodeCov for code coverage
Trying to build your fork in the cloud? Check this how-to