Red Hat CERTIFICATE SYSTEM 7.3 - ADMINISTRATION, Administration Manual

Page: 107 / 554

Monitoring Logs
85
Additionally, certain log features that are available to the other subsystems' logs do not apply to TPS
logging:
• Log rotation
• Log signing
• Registering and deleting log modules
• Buffered logging
For each log generated by a TPS instance, there are three parameters which can be configured:
•
enable
, which sets whether the log is generated.
•
filename
, which sets the name and location of the log.
•
level
, which sets the log level, the amount of information, and types of events logged. The log
level is a number between
0
and
10
. The log levels are described in
Section 3.9.3, “Log Levels
(Message Categories)”
.
Since the TPS subsystem does not utilize an administrative console, the logging levels and log
information is configured directly in the
CS.cfg
file. The following parameters configure the three TPS
logs:
logging.audit.enable=true
logging.audit.filename=/var/lib/rhpki-tps/logs/tps-audit.log
logging.audit.level=10
logging.debug.enable=true
logging.debug.filename=/var/lib/rhpki-tps/logs/tps-debug.log
logging.debug.level=7
logging.error.enable=true
logging.error.filename=/var/lib/rhpki-tps/logs/tps-error.log
logging.error.level=10
3.9.9. Monitoring Logs
To troubleshoot the subsystem, check the error or informational messages that the server has logged.
Examining the log files can also monitor many aspects of the server's operation. Some log files can
be viewed through the Console or by opening the files directly. See
Section 3.9.1, “About Logs”
for
information on the location of logs and the log files available.
To view the contents of an active or rotated system log file:
1. Log into the Console.
2. Select the
Status
tab.
3. Under
Logs
, select the log to view.
4. Set the viewing preferences in the
Display Options
section.
•
Entries
. The maximum number of entries to be displayed. When this limit is reached, the
Certificate System returns any entries that match the search request. Zero (0) means no
messages are returned. If the field is blank, the server returns every matching entry, regardless
of the number found.