You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The log file (chapi.log) is voluminous. Every call and result is recorded, up to 250 characters. The truly relevant information is sometimes unavailable because it occurs after the 250th character. For instance, the subject of the call, like a slice or project, sometimes isn't shown in the log file, but the detailed options and match terms are shown.
Consider how to make the log file less voluminous so that it is more useful. Maybe only error returns need to be logged. And maybe only the subject and other truly relevant information needs to be displayed for each invocation.
The text was updated successfully, but these errors were encountered:
The log file (chapi.log) is voluminous. Every call and result is recorded, up to 250 characters. The truly relevant information is sometimes unavailable because it occurs after the 250th character. For instance, the subject of the call, like a slice or project, sometimes isn't shown in the log file, but the detailed options and match terms are shown.
Consider how to make the log file less voluminous so that it is more useful. Maybe only error returns need to be logged. And maybe only the subject and other truly relevant information needs to be displayed for each invocation.
The text was updated successfully, but these errors were encountered: