How to make /log option less verbose?

Hello,

I am using WinSCP.exe in an NT shell script, and it is working nicely. I use the /log=C:\MyLogFile.log option. The problem is that WinSCP provides "too much information" (as they say in America!).

Is there a way to specify that the logs be less verbose?

Thanks in advance.
Tim

Try using XML logging.

A follow-up question about logging to a file. At the following page...
https://winscp.net/eng/docs/logging
... it says the following:

Text log: Events are logged in unstructured form with configurable level of verbosity.

How do I configure the level of verbosity?

Thanks
Flatlander

https://winscp.net/eng/docs/ui_pref_logging
Though note that the default level is the lowest one.
(EDIT 2022 – not anymore, there's now additional Reduced log level)

The verbosity of the logging really does make it hard to use. It would be nice if upon error the log dumped all these details but with success was more succinct, for example just listing the open/close and files transferred. It reads like a debug log. Is it possible some form of non xml simple logging could be added?

nealobrien wrote:

It reads like a debug log.

That's what it is.

Is it possible some form of non xml simple logging could be added?

XML can be converted to anything you like easily. E.g. using XSLT.

It would be very helpful to have a less verbose (non-xml) logging option. A log with logon/logoff, commands, what files have been moved, and any failures and close/exit. Is this an unrealistic/not-going-to-happen request? Its just that the current debug log is hard to use at all and it grows so fast it has to be backed up frequently.

@nealobrien: I do not think I like an idea of having third log file format.

See also Issue 1637 – Low logging level

nealobrien wrote:

It would be very helpful to have a less verbose (non-xml) logging option. A log with logon/logoff, commands, what files have been moved, and any failures and close/exit. Is this an unrealistic/not-going-to-happen request? Its just that the current debug log is hard to use at all and it grows so fast it has to be backed up frequently.

I 100% agree. Usually for scripted commands these are so they can transfer files over night when our Systems/Network are not being used, so we would like logging to know what it's actually moved/deleted and not anything on a debugging level as it makes the logs so hard to understand when just wanting to see if it's moved something. It gets confusing when it compares it, says if it's going to ignore it or not etc. When all we need is the actual change/action it's doing to a file.

Also when viewing it from the command screen without logging to a file it shows you all the files including their full paths, but as it moves so quickly you don't know what it's doing (comparing, moving, anything else etc...). It also at one point just shows you file names, I guess this is actually coping them at this point but as there is no file path to go with it, I have no idea what it's doing or moving specifically. We have many directories with the same files in them for our customers and we can't tell what customer has been copied specifically.

Even the guides are confusing with not very many examples, just more "text". The saying "Pictures paint 1000 words" comes to mind with examples:

To enable logging to a file, check Enable session logging on level.

Where's the example of what Enable Session logging on level is?

To increase a verbosity of the session log, select Debug 1 or Debug 2 level. You will probably need these (together with a logging to file), when reporting bugs only. To decrease a verbosity of the session log, select Reduced level

Does this mean set /loglevel=0, /loglevel=-1, /loglevel=-2. How low does it go.

These are all rhetorical questions of possible thoughts going through the users mind. Not everyone is on a developer mind set but actually want to use the product clearly.

Abdam wrote:

Where's the example of what Enable Session logging on level is?

There's a screenshot on the very page you quote:
https://winscp.net/eng/docs/ui_pref_logging

Does this mean set /loglevel=0, /loglevel=-1, /loglevel=-2. How low does it go..

The values of the /loglevel switch are documented in the /loglevel switch documentation:
https://winscp.net/eng/docs/commandline#loglevel

I also want a log level with just date, time and file handling success/failure. I don't need to see settings/options/preferences in the log file. I only want to see transaction level logging.
level -1 isn't enough and level 0 is WAY too verbose. Level 1 and 2 seem only good for a WinSCP developer or support person.

Most programmers that have been using it for so long, they communicate with users that haven't studied every aspect of it in sort of a "you're an idiot" tone. It is rare to find developers that "see it from the users side". Please strive to become one of those.

@guitarzan8: What do you miss at the -1 level?