VerbosityLevel

This is the standard we use everywhere in our applications. You can set the verbosity in the Sales32c.INI file, and that is the default level of logging when the application starts. In most applications, this is the only place you can set this value. With our middleware components (SalesEZ, BookEZ, TallyEZ, RentEZ applications), you can also adjust the verbosity “live” by using the Service monitor. The other special thing about the middleware applications is that even if you start with a verbosity 5 in the EZ.INI file, Pool still sets it back to 0 in six hours. Pool does this when you alter the verbosity level during operation as well.

Below are the verbosity levels and what effect they are supposed to have in the logs. In most cases this is true. However, there are exceptions and sometimes the developers did not include all the proper logging.

• 1 - Log the entry into each method in the code as well as all events at verbosity level 0. Some methods are not logged for performance and log readability reasons.

• 2 - Log the exit from a method and, when possible, the return value from that method. Also log everything from Verbosity Levels 0 and 1.

Note: This is the minimum level in Sales. Even if you set the level to 0 or 1, Sales overrides it and sets it to 2.

• 3 - Developer discretion – Log things at key points or steps in the method. Also log everything from verbosity levels 0, 1 and 2.

• 4 - Developer discretion – Log things that are interesting in the method. Also log everything from verbosity levels 0, 1, 2 and 3.

• 5 - Developer Discretion – Log everything that can help debug or trace a problem. This may include very long entries, and creates a very busy log file. This is the maximum verbosity level in all the middleware components. Also log everything from verbosity levels 0, 1, 2, 3 and 4.

• 6 - Ludicrous Level – Similar to level 5 except it includes things that may be in tight loops (meaning many, many log lines). This is only available in Sales.