Yes, this is possible but has a minimum version requirement. You must be using NLog.Extensions.Logging >= 1.5.0. Note that for ASP.NET Core applications this will be installed as a dependency if you install NLog.Web.AspNetCore >= 4.8.2. You can then create an NLog section in appsettings.json and load it with the following code: var config = … Read more
You seem to be missing the parameters that are to be inserted. See the examples at http://justinpdavis.blogspot.com/2010/04/logging-to-database-with-nlog.html The nLog web page doesn’t make it very clear that these are required, but if you squint your eyes and read https://github.com/nlog/NLog/wiki/Database-target you should find that they are required.
You can achieve that by creating a target like this: <target name=”logfile” xsi:type=”File” fileName=”${specialfolder:folder=ApplicationData}/LogFile.txt”/> The documentation can be found here. I hope this helps.
The solution is: <logger name=”Component.*” maxlevel=”Info” final=”true” /> You basically say, for logger(s) X, I want to skip all log entries that match Info or lower as this does not have the writeTo attribute. It is documented here: https://github.com/nlog/NLog/wiki/Configuration-file With the sample: <logger name=”Name.Space.*” minlevel=”Debug” maxlevel=”Error” final=”true” />
Probably too late to help you, but I believe all you need to do is include the date in the file name using the date layout renderer with the proper date format. By including the date, you don’t need to specify the archive features. When the date changes, a new file will be automatically created. … Read more
The second post on this thread led me to the solution: http://nlog-project.org/forum.html#nabble-td1685349 You have to get the current NLog configuration, make changes to this LoggingConfiguration object, then assign it back to LogManager.Configuration. This is the code I used: LoggingConfiguration config = LogManager.Configuration; var logFile = new FileTarget(); config.AddTarget(“file”, logFile); logFile.FileName = fileName + “.log”; logFile.Layout … Read more
I’ve had this issue too. As mentioned by genki you are probably logging into the \Windows\System32 directory. Maybe check for the log file you are expecting there first. When writing services I’ve often put a line like this in the beginning to get the current directory to behave like a normal application Directory.SetCurrentDirectory(AppDomain.CurrentDomain.BaseDirectory);
It looks like the problem is the shortdate in your filename definition. See my answer at this question: Delete log files after x days You have to define the filename without the date part fileName=”${basedir}/logs/Log.info.txt
Although a very old question, the same question has been haunting me this last couple of weeks. Here is my little contribution to the hive-mind: I found that for a lightweight client or client/server application using a simplistic, lightweight log viewer like log2console with NLogViewer target’ filled with additional parameters fields made it both easy … Read more
Add or replace the ${exception} tag in the layout config to ${exception:format=tostring} <targets> <target name=”errorLogFile” xsi:type=”File” fileName=”errors.txt” layout=”${message} ${exception:format=tostring}”/> </targets>