FileTarget Class

Initializes a new instance of the FileTarget class.

Initializes a new instance of the FileTarget class.

Gets or sets the size in bytes above which log files will be automatically archived.

Gets or sets a value specifying the date format to use when archiving files.

Gets or sets a value indicating whether to automatically archive log files every time the specified time passes.

Is the ArchiveFileName an absolute or relative path?

Gets or sets the name of the file to be used for an archive.

Gets or sets the way file archives are numbered.

Gets or sets a value indicating whether to archive old log file on startup.

Gets or sets a value of the file size threshold to archive old log file on startup.

Gets or sets a value indicating whether to automatically flush the file buffers after each log message.

Gets or sets the log file buffer size in bytes.

Cleanup invalid values in a filename, e.g. slashes in a filename. If set to true, this can impact the performance of massive writes. If set to false, nothing gets written when the filename is wrong.

Gets or sets the delay in milliseconds to wait before attempting to write to the file again.

Gets or sets the number of times the write is appended on the file before NLog discards the log message.

Gets or sets a value indicating whether concurrent writes to the log file by multiple processes on the same host.

Gets or sets a value indicating whether to create directories if they do not exist.

Gets or sets a value indicating whether to delete old log file on startup.

Gets or sets whether or not this target should just discard all data that its asked to write. Mostly used for when testing NLog Stack except final write

Gets or sets a value indicating whether to compress archive files into the zip archive format.

Gets or sets a value indicating whether to enable log file(s) to be deleted.

Gets or sets the file encoding.

Gets or sets the file attributes (Windows only).

Used to compress log files during archiving. This may be used to provide your own implementation of a zip file compressor, on platforms other than .Net4.5. Defaults to ZipArchiveFileCompressor on .Net4.5 and to null otherwise.

Gets or sets the name of the file to write to.

Is the FileName an absolute or relative path?

Gets or sets the footer.

Gets or set a value indicating whether a managed file stream is forced, instead of using the native implementation.

Gets or sets a value indicating whether file creation calls should be synchronized by a system global mutex.

Gets or sets the header.

Gets a value indicating whether the target has been initialized.

Gets or sets a value indicating whether to keep log file open instead of opening and closing it on each logging event.

Gets or sets the text to be rendered.

Gets or sets the line ending mode.

Gets the logging configuration this target is part of.

Gets or sets the maximum days of archive files that should be kept.

Gets or sets the maximum number of archive files that should be kept.

Gets or sets the name of the target.

Gets the characters that are appended after each line.

Gets or sets the number of files to be kept open. Setting this to a higher value may improve performance in a situation where a single File target is writing to many files (such as splitting by level or by logger).

Gets or sets the maximum number of seconds that files are kept open. Zero or negative means disabled.

Gets or sets the maximum number of seconds before open files are flushed. Zero or negative means disabled.

Gets or sets a value indicating whether to replace file contents on each write instead of appending log message at the end.

Gets the object which can be used to synchronize asynchronous operations that must rely on the .

Gets or sets a value indicating whether to write BOM (byte order mark) in created files. Defaults to true for UTF-16 and UTF-32

Gets or sets a value indicating whether the footer should be written only when the file is archived.

Gets or sets whether to write the Header on initial creation of file appender, even if the file is not empty. Default value is , which means only write header when initial file is empty (Ex. ensures valid CSV files)

Calculate the DateTime of the requested day of the week.

Removes records of initialized files that have not been accessed in the last two days.

Removes records of initialized files that have not been accessed after the specified date.

Closes the file(s) opened for writing.

Closes the target.

Releases unmanaged and - optionally - managed resources.

Flush any pending log messages (in case of asynchronous targets).

Flushes all pending file operations.

Initializes file logging by creating data structures that enable efficient multi-file logging.

Calls the Precalculate(LogEventInfo) on each volatile layout used by this target. This method won't prerender if all layouts in this target are thread-agnostic.

Formats the log event for write.

Gets the bytes to be written to the file.

Renders the logevent into a string-result using the provided layout

Renders the logevent into a result-value by using the provided layout

Resolve from DI ServiceRepository

Returns a string that represents the current object.

Modifies the specified byte array before it gets sent to a file.

Writes async log event to the log target.

Writes the specified array of logging events to a file specified in the FileName parameter.

Writes the specified logging event to a file specified in the FileName parameter.

Writes the log to the target.

Writes the array of log events.

Writes the array of log events.

Writes a log event to the log target, in a thread safe manner. Any override of this method has to provide their own synchronization mechanism. !WARNING! Custom targets should only override this method if able to provide their own synchronization mechanism. Layout-objects are not guaranteed to be thread-safe, so using them without a SyncRoot-object can be dangerous.

Writes an array of logging events to the log target, in a thread safe manner. Any override of this method has to provide their own synchronization mechanism. !WARNING! Custom targets should only override this method if able to provide their own synchronization mechanism. Layout-objects are not guaranteed to be thread-safe, so using them without a SyncRoot-object can be dangerous.

LogEvent is written to target, but target failed to successfully initialize