You need to have mapped a logging
directory during BlueCat Gateway installation. Refer to the Installing BlueCat Gateway section in the BlueCat Gateway
Installation Guide. If you did not map a logging directory, all logs will be written
inside the container by default and will be deleted when you restart the
container.
-
Log in to BlueCat Gateway.
-
Select .
-
Click Log Settings.
-
In the Session Logging Format field, enter a path.
The path in the
log_session_path variable
is relative to the logging directory mapped
during
installation.
[%(asctime)s][PID:%(process)d][{username}] %(levelname)s: %(message)s
-
In the Session Logging Level select one of the following
options: DEBUG, INFO, WARNING, ERROR, CRITICAL, or NOTSET.
Attention: By default, the session level is set to Debug. Before
deploying BlueCat Gateway into a production environment,
select the logging level that best suits the needs of your
environment.
-
(Optional) - Select the Enable Redirect
to Standard Out check box to log to Standard Out instead of to a
directory. The logs directed to Standard Out are caught by the Apache ErrorLog,
and will appear in the errors.log file specified in your
virtual host file.
-
Complete this step only if you did not Enable
Redirect to Standard Out. In
the Session Logging Path field, enter the path to the
logging directory mapped during the BlueCat Gateway
installation.
-
In the Session Logging Timestamp Format field, enter a
format.
For example:
log_session_timestamp_format = '%Y-%m-%dT%H:%M:%SZ'
-
In the Log File Timestamp Format field, enter a
format.
For example:
log_file_timestamp_format = '%Y-%m-%dT%H%M%S%fZ'
-
Click Save.
Note: Changes will take affect only for new user sessions