Forwarding logs to remote log servers

Deployment options: IBM Netezza Appliance

Learn how to integrate Netezza Performance Server 11.2.2.X and later with a remote log server and redirect system logs to the remote log server system.

Procedure

  1. Log in to the container as root by using one of the following commands: 
    • oc exec -it ipshost-0 -n NAMESPACE_NAME -- bash
    • ssh root@DEDICATED NPS_IP -p 51022
  2. Inside the container, test the reachability of remote system to which you plan to upload the logs by running the telnet command against that system.

    You need the remote log server IP address to run the command.

    The default port is 514.

    telnet REMOTE_IP_SERVER PORT
  3. Append the entry to the /etc/rsyslog.d/customrsyslog.conf file in the following format: 
    $ActionQueueFileName UNIQUE NAME    
$ActionQueueMaxDiskSpace 1g           
$ActionQueueSaveOnShutdown on     
$ActionQueueType LinkedList           
$ActionResumeRetryCount -1            
Facility.Priority @@<REMOTE_SERVER_IP:PORT #Forwarding Rule
    Example: 
    $ActionQueueFileName fwdRule1     
$ActionQueueMaxDiskSpace 1g           
$ActionQueueSaveOnShutdown on     
$ActionQueueType LinkedList           
$ActionResumeRetryCount -1    
cron.crit @@9.30.189.177:514
  4. Restart the rsyslog daemon. 
    systemctl restart rsyslog

    The custom /etc/rsyslog.d/customrsyslog.conf dropin file is a symlink to persistent file on all Cloud Pak for Data System 2.0.X systems. The customization is not lost after you restart the pod.