If the text file is already formatted using the
For example,
CLOG_TEXT_LOG[2]=/var/adm/app/logs/app.log
CLOG_TEXT_FORMAT[2]="syslog"
If no CLOG_TEXT_FORMAT[]entry is made for a corresponding
CLOG_TEXT_LOG[]entry, the default is “custom”.
For an example of a file in syslogformat, see the actual system log file /var/adm/
syslog/syslog.log.
3.After completing the required edits, there are two ways to initiate forwarding for the new log files:
•Restarting
•Manual restart, that does not disrupt
The procedures are the following:
•Restart
This will disrupt
•Start the clog_tail process manually for the text log file.
If the text log file is in syslog format, use the following command:
/opt/dsau/bin/clog_tail
If the text log file is in a custom format, use the following command:
/opt/dsau/bin/clog_tail
For example, for a log called myapp.log in custom format, the following command starts clog_tail:
# /opt/dsau/bin/clog_tail
If the system is a Serviceguard cluster, copy the edited /etc/rc.config.d/
#
Either restart
3.3.2.3.3.2 Consolidating Text Logs on the Log Consolidation Server
To consolidate the text logs forwarded from clients to a Log Consolidation Server, complete the following tasks on the Log Consolidation Server:
1.For each text log that will be forwarded from a client, add the following destination, filter and log lines to the file
HP_AUTOMATED_LOG_FILE_CONSOLIDATION:
For the destination line:
destination d_node1_text1{ file(“fs/textdir/node1_text1.log”); };
For the filter line:
filter f_node1_text1{ program(node1_text1.log); };
3.3 Log Consolidation Configuration | 73 |