The function start/1 starts the rb_server
with the specified options, while start/0 starts with
default options. The rb_server must be started before
reports can be browsed. When the rb_server is
started, the files in the specified directory are
scanned. The other functions assume that the server has
started.
{start_log, FileName} starts logging to file. All
reports will be printed to the named file. The default is
standard_io.
{max, MaxNoOfReports}. Controls how many reports the
rb_server should read on start-up. This option is
useful as the directory may contain 20.000 reports. If this
option is given, the MaxNoOfReports latest reports
will be read. The default is 'all'.
{report_dir, DirString}. Defines the directory where
the error log files are located. The default is {sasl, error_logger_mf_dir}.
{type, ReportType}. Controls what kind of reports the
rb_server should read on start-up. ReportType
is a supported type, 'all', or a list of supported
types. The default is 'all'.
{abort_on_error, Bool}. This option specifies whether
or not logging should be aborted if rb encounters an unprintable
report. (You may get a report on incorrect form if the
error_logger function error_msg or
info_msg has been called with an invalid format string).
If Bool is true, rb will stop logging (and print an
error message to stdout) if it encounters a badly formatted report.
If logging to file is enabled, an error message will be appended to
the log file as well.
If Bool is false (which is the default value), rb will
print an error message to stdout for every bad report it
encounters, but the logging process is never aborted. All printable
reports will be written. If logging to file is enabled, rb prints
* UNPRINTABLE REPORT * in the log file at the location of an
unprintable report.