Where are the best locations to write an error log

问题:

Where would you write an error log file, say ErrorLog.txt, in Windows? Keep in mind the path would need to be open to basic users for file write permissions.

I know the eventlog is a possible location for writing errors, but does it work for "user" level permissions?

EDIT: I am targeting Windows 2003, but I was posing the question in such a way as to have a "General Guideline" for where to write error logs.
As for the EventLog, I have had issues before in an ASP.NET application where I wanted to log to the Windows event log, but I had security issues causing me heartache. (I do not recall the issues I had, but remember having them.)

回答1:

Have you considered logging the event viewer instead? If you want to write your own log, I suggest the users local app setting directory. Make a product directory under there. It's different on different version of Windows.

On Vista, you cannot put files like this under c:\program files. You will run into a lot of problems with it.

In .NET, you can find out this folder with this:

Environment.GetFolderPath(Environment.SpecialFolder.LocalApplicationData)

And the Event Log is fairly simple to use too:

http://msdn.microsoft.com/en-us/library/system.diagnostics.eventlog.aspx

回答2:

Text files are great for a server application (you did say Windows 2003). You should have a separate log file for each server application, the location is really a matter of convention to agree with administrators. E.g. for ASP.NET apps I've often seen them placed on a separate disk from the application under a folder structure that mimics the virtual directory structure.

For client apps, one disadvantage of text files is that a user may start multiple copies of your application (unless you've taken specific steps to prevent this). So you have the problem of contention if multiple instances attempt to write to the same log file. For this reason I would always prefer the Windows Event Log for client apps. One caveat is that you need to be an administrator to create an event log - this can be done e.g. by the setup package.

If you do use a file, I'd suggest using the folder Environment.SpecialFolder.LocalApplicationData rather than SpecialFolder.ApplicationData as suggested by others. LocalApplicationData is on the local disk: you don't want network problems to stop you from logging when the user has a roaming profile. For a WinForms application, use Application.LocalUserAppDataPath.

In either case, I would use a configuration file to decide where to log, so that you can easily change it. E.g. if you use Log4Net or a similar framework, you can easily configure whether to log to a text file, event log, both or elsewhere (e.g. a database) without changing your app.

回答3:

Personally, I would suggest using the Windows event log, it's great. If you can't, then write the file to the ApplicationData directory or the ProgramData (Application Data for all users on Windows XP) directory.

回答4:

The standard location(s) are:

C:\Documents and Settings\All Users\Application Data\MyApp

or

C:\Documents and Settings\%Username%\Application Data\MyApp

(aka %UserProfile%\Application Data\MyApp) which would match your user level permission requirement. It also separates logs created by different users.

Using .NET runtime, these can be built as:

AppDir=
  System.Environment.GetFolderPath(Environment.SpecialFolder.CommonApplicationData)

or

AppDir=
  System.Environment.GetFolderPath(Environment.SpecialFolder.ApplicationData)

followed by:

MyAppDir = IO.Path.Combine(AppDir,'MyApp')

(Which, hopefully, maps Vista profiles too).

回答5:

The Windows event log is definitely the way to go for logging of errors. You're not limited to the "Application" log as it's possible to create a new log target (e.g. "My Application"). That may need to be done as part of setup as I'm not sure if it requires administrative privileges or not. There's a Microsoft example in C# at http://support.microsoft.com/kb/307024.

Windows 2008 also has Event Log Forwarding which can be quite handy with server applications.

回答6:

I agree with Lou on this, but I prefer to set this up in a configuration file like Joe said. You can use

file value="${APPDATA}/Test/log-file.txt"

("Test" could be whatever you want, or removed entirely) in the configuration file, which causes the log file to be written to "/Documents and Settings/LoginUser/Application Data/Test" on Windows XP and to "/Users/LoginUser/AppData/Roaming/Test on Windows Vista.

I am just adding this as I just spent way too much time figuring how to make this work on Windows Vista...

This works as-is with Windows applications. To use logging in web applications, I found Phil Haack's blog entry on this to be a great resource: http://haacked.com/archive/2005/03/07/ConfiguringLog4NetForWebApplications.aspx

回答7:

%TEMP% is always a good location for logs I find.

回答8:

Going against the grain here - it depends on what you need to do. Sometimes you need to manipulate the results, so log.txt is the way to go. It's simple, mutable, and easy to search.

Take an example from Joel. Fogbugz will send a log / dump of error messages via http to their server. You could do the same and not have to worry about the user's access rights on their drive.

回答9:

I personally don't like to use the Windows Event Log where I am right now because we do not have access to the production servers, so that would mean that we would need to request access every time we wanted to look at the errors. It is not a speedy process unfortunately, so your troubleshooting is completely haulted by waiting for someone else. I also don't like that they kind of get lost within the ones from other applications. Sure you can sort, but it's just a bit of a nucance scrolling down. What you use will end up being a combination of personal preference coupled along with limitations of the enviroment you are working in. (log file, event log, or database)

回答10:

Put it in the directory of the application. The users will need access to the folder to run and execute the application, and you can check write access on application startup.

The event log is a pain to use for troubleshooting, but you should still post significant errors there.

EDIT - You should look into the MS Application Blocks for logging if you are using .NET. They really make life easy.

Jeez Karma-killers. Next time I won't even offer a suggestion when the poster puts up an incomplete post.