Hello,

I need the possibility to create a log for each tasks.
A new tab log in each task for choose :
verbose log or not, rotation parameter...
I need this log for example in file manipulation (copy, delete...), ftp transfert and other.

Thanks

Patrick

Do you need a file or do you need historic access only. We are thinking about saving Task logs historically in a database so you can pick them up later. And save/export the log if you want.

---

The VC team should consider including the log4net library (http://logging.apache.org/log4net/index.html) or similar as part of VC; the log appenders that are available would satisfy most needs.

If a db logging ability is on the cards PLEASE engineer the solution so that multiple instances of VC can log into the same db space.

Anton du Toit

The VC team should consider including the log4net library (http://logging.apache.org/log4net/index.html) or similar as part of VC; the log appenders that are available would satisfy most needs.

If a db logging ability is on the cards PLEASE engineer the solution so that multiple instances of VC can log into the same db space.

Anton du Toit

Can you elaborate more what is interesting about Log4Net and how you would use it if it was implemented in VC?

When we are talking about DB loggin we are talking about loggin Server events - not Client events. What do you mean with multiple VC instances? You mean several Servers?

---

Hello Henrik,
For the moment, I need files logs (per hour, per day ...) but I think db log is a good idea for other users needs.
A normal log can contain (for example for a copy file or file tranfert) date hour of start, date of end with number of files copied/transfered, errors.
A verbose log list all the file copied, transfered in error.

Thanks

Patrick

When we are talking about DB loggin we are talking about loggin Server events - not Client events. Yes
What do you mean with multiple VC instances? You mean several Servers? Yes, the ability to consolidate all logging from multiple instances of VC running on different servers to a centralized log.

Can you elaborate more what is interesting about Log4Net and how you would use it if it was implemented in VC?

Henrik I am not advocating log4net as the only logging framework, it does however provide you with an idea of what can be achieved.

* log4net provides the ability to re-direct logging output to already developed log appenders. Not all will be relevant in the VC context

log4net.Appender.AdoNetAppender
log4net.Appender.AnsiColorTerminalAppender
log4net.Appender.AspNetTraceAppender
log4net.Appender.ColoredConsoleAppender
log4net.Appender.ConsoleAppender
log4net.Appender.EventLogAppender
log4net.Appender.FileAppender
log4net.Appender.LocalSyslogAppender
log4net.Appender.MemoryAppender
log4net.Appender.NetSendAppender
log4net.Appender.OutputDebugStringAppender
log4net.Appender.RemoteSyslogAppender
log4net.Appender.RemotingAppender
log4net.Appender.RollingFileAppender
log4net.Appender.SmtpAppender
log4net.Appender.TelnetAppender
log4net.Appender.TraceAppender
log4net.Appender.UdpAppender

*The ability to natively re-direct log output to more appropriate destinations without having to develop scripts to parse and re-direct output from the current VC log files. Depending on implementation you could re-direct log output of a Job/Task to a specific log appender(s).

*The ability the stream different log messages to different destinations – debug messages to a RollingFile Appender, error messages to an EventLog Appender etc.

*The ability to filter/suspress log output.

*log4net XML config file is easily configurable and provides the VC SysAdmin with the ability to control exactly what must happen to log output.

*The dissociation of log management to VC. There is no required “smarts” with-in VC to write to Syslogs, Eventlogs, Files or whatever new appender maybe developed.

Ultimately it is about giving the VC SysAdmin the flexibility and control over log output. Many VC users may not see the benefit but it goes to managing multiple servers each with many job/tasks. It is ability to centralize output, filter through the noise and act on any problems.