is NLog still popular?
-
I plan to add logging into my Windows Form application. NLog is still looking good for me in my case. are there any people still using it from codeproject community?
diligent hands rule....
I use nlog - I prefer it to log4net. It's very easily configured, and comes with pre-canned formatters for most situations that you can think of.
-
I plan to add logging into my Windows Form application. NLog is still looking good for me in my case. are there any people still using it from codeproject community?
diligent hands rule....
Yes, NLog is still popular and we use it with some of our websites and applications. If you are using AWS, as we do with most of our websites and apps, you can log your data/errors, if you want, to https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/WhatIsCloudWatchLogs.html[^]
-
I plan to add logging into my Windows Form application. NLog is still looking good for me in my case. are there any people still using it from codeproject community?
diligent hands rule....
The better question is, should I do logging? Seriously. I'm not being facetious. Logging sounds great until, as I've always experienced, there are reams of output to wade through and nobody bothers and they even forget there's logging going on. What is it you need to log, and when exactly does it need to be logged? Now granted, years ago my team added logging to every user action (this was a DOS desktop app at that) which was enabled in "QA" mode. We logged the tester's activity, we were able to play it back, and when they said "I did x, y, and z" we could look at the log and say, "no, you did x, A and z" and they were stunned. So that kind of logging was quite useful! :laugh:
Latest Article:
Create a Digital Ocean Droplet for .NET Core Web API with a real SSL Certificate on a Domain -
The better question is, should I do logging? Seriously. I'm not being facetious. Logging sounds great until, as I've always experienced, there are reams of output to wade through and nobody bothers and they even forget there's logging going on. What is it you need to log, and when exactly does it need to be logged? Now granted, years ago my team added logging to every user action (this was a DOS desktop app at that) which was enabled in "QA" mode. We logged the tester's activity, we were able to play it back, and when they said "I did x, y, and z" we could look at the log and say, "no, you did x, A and z" and they were stunned. So that kind of logging was quite useful! :laugh:
Latest Article:
Create a Digital Ocean Droplet for .NET Core Web API with a real SSL Certificate on a DomainI think logging exceptions and/or unexpected errors is a must, especially for debugging purposes. I am not really into informational logging in a Prod environment; maybe, in dev, but not prod. we have a pageview table that stores all the page view stuff for troubleshooting and metrics for business team.
-
I plan to add logging into my Windows Form application. NLog is still looking good for me in my case. are there any people still using it from codeproject community?
diligent hands rule....
I still use it - can't see a reason not to
"Life should not be a journey to the grave with the intention of arriving safely in a pretty and well-preserved body, but rather to skid in broadside in a cloud of smoke, thoroughly used up, totally worn out, and loudly proclaiming “Wow! What a Ride!" - Hunter S Thompson - RIP
-
The better question is, should I do logging? Seriously. I'm not being facetious. Logging sounds great until, as I've always experienced, there are reams of output to wade through and nobody bothers and they even forget there's logging going on. What is it you need to log, and when exactly does it need to be logged? Now granted, years ago my team added logging to every user action (this was a DOS desktop app at that) which was enabled in "QA" mode. We logged the tester's activity, we were able to play it back, and when they said "I did x, y, and z" we could look at the log and say, "no, you did x, A and z" and they were stunned. So that kind of logging was quite useful! :laugh:
Latest Article:
Create a Digital Ocean Droplet for .NET Core Web API with a real SSL Certificate on a Domainyour question is great: my first step is to log some data files that are empty. I downloaded these kinds of files using web API. I need to know what kind of files are empty. later on I will go deeper to record exceptions.
diligent hands rule....
-
I think logging exceptions and/or unexpected errors is a must, especially for debugging purposes. I am not really into informational logging in a Prod environment; maybe, in dev, but not prod. we have a pageview table that stores all the page view stuff for troubleshooting and metrics for business team.
Slacker007 wrote:
I think logging exceptions and/or unexpected errors is a must, especially for debugging purposes.
Agreed. I've actually become rather brutal about it - I send an email to myself when something critical blows up. I have a few Outlook rules as a result. :laugh:
Latest Article:
Create a Digital Ocean Droplet for .NET Core Web API with a real SSL Certificate on a Domain -
I plan to add logging into my Windows Form application. NLog is still looking good for me in my case. are there any people still using it from codeproject community?
diligent hands rule....
Nop, I always roll my own.
-
Nop, I always roll my own.
just write message into a text file? it turns out my case is simple. I just dump my messages into a text file, which file name is with timestamp.
diligent hands rule....
-
The better question is, should I do logging? Seriously. I'm not being facetious. Logging sounds great until, as I've always experienced, there are reams of output to wade through and nobody bothers and they even forget there's logging going on. What is it you need to log, and when exactly does it need to be logged? Now granted, years ago my team added logging to every user action (this was a DOS desktop app at that) which was enabled in "QA" mode. We logged the tester's activity, we were able to play it back, and when they said "I did x, y, and z" we could look at the log and say, "no, you did x, A and z" and they were stunned. So that kind of logging was quite useful! :laugh:
Latest Article:
Create a Digital Ocean Droplet for .NET Core Web API with a real SSL Certificate on a DomainGenerally it is useful to use logging on different levels and enable/disable the levels as needed. There might be no need to see any informational messages in certain applications until there is a certain error that you want to inspect. In other cases it might be useful to see verbose things like "user x did action y" all the time. As a rule of thumb I would only log things to which I had a specific use-case in mind or things I knew from experience that they help down the line. Regarding if logging should be done in general: Yes, please. As someone who writes and uses tools that go through logs all the time I am very grateful for applications that log well - meaning not too much, but at least all errors and warnings. If you use Windows then you could think about writing events to an eventlog instead of writing text files tho.
-
Generally it is useful to use logging on different levels and enable/disable the levels as needed. There might be no need to see any informational messages in certain applications until there is a certain error that you want to inspect. In other cases it might be useful to see verbose things like "user x did action y" all the time. As a rule of thumb I would only log things to which I had a specific use-case in mind or things I knew from experience that they help down the line. Regarding if logging should be done in general: Yes, please. As someone who writes and uses tools that go through logs all the time I am very grateful for applications that log well - meaning not too much, but at least all errors and warnings. If you use Windows then you could think about writing events to an eventlog instead of writing text files tho.
great sharing.
diligent hands rule....
-
The better question is, should I do logging? Seriously. I'm not being facetious. Logging sounds great until, as I've always experienced, there are reams of output to wade through and nobody bothers and they even forget there's logging going on. What is it you need to log, and when exactly does it need to be logged? Now granted, years ago my team added logging to every user action (this was a DOS desktop app at that) which was enabled in "QA" mode. We logged the tester's activity, we were able to play it back, and when they said "I did x, y, and z" we could look at the log and say, "no, you did x, A and z" and they were stunned. So that kind of logging was quite useful! :laugh:
Latest Article:
Create a Digital Ocean Droplet for .NET Core Web API with a real SSL Certificate on a DomainHaving supported numerous systems, I can tell you that Logging Matters. And with current day abilities to create date/time files, and delete files over 7 days old, etc. I am fine. The one issue we ran into was needing INSANE levels of logging to track down a DEEP bug. 7 Days worth of this would overwhelm ANY system. (Think of it as turning on Kernel Debugging) So, we implemented an in-memory circular log for that level of debugging, and NEVER wrote it to disk, until an exception occurred. So, we had all of our "good logging", and then we had an INSANE level, that would usually cover the last couple of minutes before an exception. (to be clear, we trapped the exception, and added that logging information to the output, along with a stack trace). Within a few days we had a rare problem isolated (something that happened about every 10,000 sessions). Yes, we need logging. But be careful, I've seen people logging DB connection credentials! OUCH!
-
just write message into a text file? it turns out my case is simple. I just dump my messages into a text file, which file name is with timestamp.
diligent hands rule....
Pretty much. Maybe :) I don't use logging packages (well, I did in another development life). I live in the embedded world, and for the last slate of products, we rolled our own. I won't get into writing stuff to the file system and worrying about loss of power. What I will tell you to do is to use a comma delimited format for your logging. Think ahead of time what information is useful to you and set up standards. Error levels, associated data. But keep it all comma delimited. Being able to suck this into Excel is priceless.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
