Logging communication using LogWriter 

Communication logs are very useful when troubleshooting issues at the FTP protocol or communication level. Whenever you run into a problem, a log makes it possible to see what is going on.

To start logging, just add the following line into your code (just after creating the Ftp object):

// create an FTP object
var ftp = new Rebex.Net.Ftp();

// start logging to a file
ftp.LogWriter = new Rebex.FileLogWriter(@"C:\MyData\log.txt");

' create an FTP object
Dim ftp As New Rebex.Net.Ftp()

' start logging to a file
ftp.LogWriter = New Rebex.FileLogWriter("C:\MyData\log.txt")

A sample log file:

2013-05-23 16:13:37.435 Opening log file.
2013-05-23 16:13:37.436 Using FileLogWriter version 2.0.0.0.
2013-05-23 16:13:37.503 INFO Ftp(1)[8] Info: Connecting to testserver.local:21 using Ftp 4.0.0.0.
2013-05-23 16:13:37.504 INFO Ftp(1)[8] Info: Using proxy none.
2013-05-23 16:13:37.550 DEBUG Ftp(1)[8] Info: Connection succeeded.
2013-05-23 16:13:37.556 INFO Ftp(1)[8] Response: 220 Microsoft FTP Service

Log verbosity levels 

There are several levels of log verbosity:

• Error - logs error messages only
• Info - default level; logs important informative messages as well
• Debug - logs all messages useful for debugging purposes
• Verbose - very detailed log for advanced analysis; logs content of communication packets
  Warning: At the Verbose level, user credentials are written to the log as well.

To specify a log level, just pass an argument to FileLogWriter's constructor:

// start logging to a file at debug level
ftp.LogWriter = new Rebex.FileLogWriter(
    @"C:\MyData\log.txt", Rebex.LogLevel.Debug);

' start logging to a file at debug level
ftp.LogWriter = New Rebex.FileLogWriter("C:\MyData\log.txt", Rebex.LogLevel.Debug)

Built-in log writers 

Text file

To log into a text file, use FileLogWriter:

// start logging to a file at debug level
ftp.LogWriter = new Rebex.FileLogWriter(
    @"C:\MyData\log.txt", Rebex.LogLevel.Debug);

' start logging to a file at debug level
ftp.LogWriter = New Rebex.FileLogWriter("C:\MyData\log.txt", Rebex.LogLevel.Debug)

.NET trace listener

To log to .NET Trace Listeners, use TraceLogWriter:

// start logging to subscribed trace listeners
ftp.LogWriter = new Rebex.TraceLogWriter(Rebex.LogLevel.Debug);

' start logging to subscribed trace listeners
ftp.LogWriter = New Rebex.TraceLogWriter(Rebex.LogLevel.Debug)

Standard output stream

To log to the standard output stream, use ConsoleLogWriter:

// start logging to the standard output stream at debug level
ftp.LogWriter = new Rebex.ConsoleLogWriter(Rebex.LogLevel.Debug);

' start logging to the standard output stream at debug level
ftp.LogWriter = New Rebex.ConsoleLogWriter(Rebex.LogLevel.Debug)

Logging to multiple log writers

To log to more log writers at the same time, use TeeLogWriter:

var consoleLogWriter = new Rebex.ConsoleLogWriter(Rebex.LogLevel.Debug);
var fileLogWriter = new Rebex.FileLogWriter(@"C:\MyData\log.txt", Rebex.LogLevel.Info);

// start logging to both console and file log writers
ftp.LogWriter = new Rebex.TeeLogWriter(consoleLogWriter, fileLogWriter);

Dim consoleLogWriter = New Rebex.ConsoleLogWriter(Rebex.LogLevel.Debug)
Dim fileLogWriter = New Rebex.FileLogWriter("C:\MyData\log.txt", Rebex.LogLevel.Debug)

' start logging to both console and file log writers
ftp.LogWriter = New Rebex.TeeLogWriter(consoleLogWriter, fileLogWriter)

Writing custom log writers 

// Sample log writer that logs to the standard error output stream
public class MyLogWriter : LogWriterBase
{
    protected override void WriteMessage(string message)
    {
        Console.Error.WriteLine("Rebex: {0}", message);
    }
}

' Sample log writer that logs to the standard error output stream
Public Class MyLogWriter
    Inherits LogWriterBase

    Protected Overrides Sub WriteMessage(message As String)
        Console.Error.WriteLine("Rebex: {0}", message)
    End Sub

End Class