Gets or sets the name of the log to read from or write to.
Assembly: System (in System.dll)
[<TypeConverterAttribute("System.Diagnostics.Design.LogConverter, System.Design, Version=220.127.116.11, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a")>] [<MonitoringDescriptionAttribute("LogLog")>] [<SettingsBindableAttribute(true)>] member Log : string with get, set
Property ValueType: System.String
The name of the log. This can be Application, System, Security, or a custom log name. The default is an empty string ("").
Three log files exist by default on the server: Application, System, and Security. Applications and services use the Application log file. Device drivers use the System log file. The system generates success and failure audit events in the Security log when auditing is turned on. If you have other applications installed, like Active Directory on Windows servers, there might be other default log files. In addition, you can create custom log files on a local or remote computer. Custom logs help organize your entries in a more detailed way than is allowed when your components write events to the default Application log.
Log names are limited to eight characters. According to the system, MyLogSample1 and MyLogSample2 are the same log.
If you write to an event log, it is not enough to specify the property. You must associate a Source property with your event log resource to connect it to a particular log. It is not necessary to specify a Source when only reading from a log, but an event source must be associated with the event log resource in the server's registry. You can specify only the name and MachineName (server computer name) to read from it.
If the Source property has not been specified, a call to returns an empty string if has not been explicitly set (by setting the property, or through the constructor). If the Source has been specified, returns the name of the log to which that source was registered.
A source can only be registered to one log at a time. If the Source property was set for an instance of EventLog, you cannot change the property for that EventLog without changing the value of Source or calling DeleteEventSource first. If you change the property after the Source property has been set, writing a log entry throws an exception.
The operating system stores event logs as files. When you use EventLogInstaller or CreateEventSource to create a new event log, the associated file is stored in the %SystemRoot%\System32\Config directory on the specified computer. The file name is set by appending the first 8 characters of the property with the ".evt" file name extension.
You cannot create a new log using the property alone (without specifying a source for the log). You can call CreateEventSource, passing in a new log name as a parameter, and then call DeleteEventSource. However, the intent is usually either to create (and write entries to) new application-specific logs, or to read from existing logs.
If the value changes, the event log is closed and all event handles are released.
If you set the property to the name of a log that does not exist, the system attaches the EventLog to the Application log, but does not warn you that it is using a log other than the one you specified.