Buffalo Surveillance Server Administrator's Manual page 228

Table of Contents

Advertisement

228
Buffalo Surveillance Server
Field
Activity log pathname
Maximum log size
Action to take when the
log reaches it maximum
size
Error log pathname
Click [ OK ] to save the new settings.
Meaning and Directions
Buffalo Surveillance Server supports event auditing,
providing a security audit trail, through activity logs.
Activity logs include following events: Vault start, Vault
stop, file read, file write, file create, file delete, media load,
media unload, and media erase. For these events, the
following information is recorded: name and IP of the user
who executed the event and the date and time the event
was executed. Activity logging is optional.
Buffalo Surveillance Server creates activity logs in tab-
delimited format. Consequently, logs can be imported into
any application that supports the tab-delimited format,
such as Microsoft Excel.
This field defines to where your activity logs will be written.
This option defines the maximum size to which the activity
log will be permitted to grow. It is important to limit the
size of the activity log because it may be difficult to find
needed the information in an overly large activity log.
This option enables you to overwrite the existing activity
log. Overwriting the activity log prevents activity log
proliferation.
If you select No for this option, a new activity log will be
created whenever the current activity log reaches the
maximum size you defined in the previous field.
Error logs are created only when a Buffalo Surveillance
Server Vault encounters a problem. Error logs include
warning and Vault start and Vault stop information. Buffalo
Surveillance Server supports error logging for every Vault in
your Information Repository, and error logging is always
enabled.
This field enables you to define where error logs will be
stored. Where "activity logs" record all Buffalo Surveillance
Server activity, "error logs" record only events that have
gone wrong. Be sure to remember where you are storing
your error logs so that you can refer to them should an
error condition occur during Buffalo Surveillance Server
processing.

Advertisement

Table of Contents
loading

Table of Contents