Go to the table of contents Go to the previous page Go to the next page Go to the index View or print as PDF
Working With Log Files > Event log file formats > Choosing binary or ASCII
*
ASCII: these files can be processed using standard, off-the-shelf log-analysis tools. However, Content Gateway must perform additional processing to create the files in ASCII, resulting in an increase in overhead. Also, ASCII files tend to be larger than the equivalent binary files. ASCII log files have a .log filename extension by default.
*
Binary: these files generate lower system overhead, as well as generally occupying less space on the disk, depending on the type of information being logged. You must, however, use a converter application before you can read or analyze these files using standard tools. Binary log files use a .blog filename extension by default.
For standard log formats, you select Binary or ASCII on the Configure > Subsystems > Logging > Formats tab in Content Gateway Manager. See Setting standard log file format options. For the custom log format, you specify ASCII or Binary mode in the LogObject. Refer to Custom format.
Note 

Go to the table of contents Go to the previous page Go to the next page Go to the index View or print as PDF
Working With Log Files > Event log file formats > Choosing binary or ASCII