AutoCommand 20036 Installationsanleitung PDF herunterladen (Seite 86)

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 nothing except some startup and shutdown messages and any errors.

2. 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.

3. 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.

4. Developer discretion – Log things at key points or steps in the method. Also log everything from verbosity

levels 0, 1 and 2.

5. Developer discretion – Log things that are interesting in the method. Also log everything from verbosity

levels 0, 1, 2 and 3.

6. Developer Discretion – Log everything that can help debug or trace a problem. This may include very long

entries, and will create 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.

7. 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.

LogInvoke=True

This setting is enabled in the EZ.INI in the [Prefs] section. (Or [Preferences ] in 4.1).This type of

logging was designed to capture both the Current (or last) call and the longest call from a given salespoint. It

created a dbf called EZ_Invoke.dbf in the pool folder (So it would be disallowed in a UAC enabled

environment). The DBF contains a single row for each connection that has made a call. When a salespoint makes a

call, the entire call string is stored in the InvokeStr column, along with the date/time that the call started. The start

time is cleared if the invoke call finishes. This is so you can determine if there is a Salespoint “stuck” in a never-

ending call. The DBF also has the longest call and the maximum duration (in seconds) stored in the MaxCallStr

and MaxInCall columns. This form of logging is now obsolete, and we do not recommend using it.

Filtered and Performance Logging

These settings are enabled by placing a specially named file, _LogDirectives.txt, in the EZ folder,

C:\ProgramData\Siriusware\Pool\EZ. The EZ checks for the existence of this file between each call

from a salespoint. If the file is detected, it is read and any supported filters or directives are put in place.

Filtered Logging

The problem this method of logging solves is, that frequently, support staff needs verbosity 5 logs to diagnose

problems. Setting the EZ verbosity to 5 can creates extremely voluminous logs that have calls from every connected

1 2 ... 81 82 83 84 85 86 87 88 89 90 91 ... 182 183

Keine Kommentare

AutoCommand 20036 Installationsanleitung Seite 86