Forwarding logs to remote log server

Deployment options: Netezza Performance Server for Cloud Pak for Data System

Learn how to integrate Netezza Performance Server with a remote log server and redirect system logs to the remote log server system. Remote log server system supports Linux OS as log source that uses Syslog services.

Before you begin

You must enable the remote logging server to accept the forwarding messages from control nodes.
Configure the external IP addresses of Cloud Pak for Data System control node on which the Netezza Performance Server host container is running. If It is not configured, then configure the external IP addresses.

Procedure

Run:

docker exec -it ipshost bash

Or:

ssh root@<ips container IP> -p 51022

Note down the remote log server IP address and test the reachability of the remote log server system inside the container.
Run the telnet command with the configured port.
```
telnet <RemoteIPServer> <Port>
```
The default port is 514.

Edit the /etc/rsyslog.conf file and append the entry at end of the file in the following format:

$ActionQueueFileName <unique Name> 	
$ActionQueueMaxDiskSpace 1g   		
$ActionQueueSaveOnShutdown on 	
$ActionQueueType LinkedList   		
$ActionResumeRetryCount -1    		
<Facility.Priority >   @@<RemoteServerIP:port>    #Forwarding Rule

Example:

$ActionQueueFileName fwdRule1 	
$ActionQueueMaxDiskSpace 1g   		
$ActionQueueSaveOnShutdown on 	
$ActionQueueType LinkedList   		
$ActionResumeRetryCount -1    
cron.crit  @@9.30.189.177:514

Restart the rsyslog daemon:
```
systemctl restart rsyslog
```
Redeploy the ipshost1 container on the remaining control plane nodes and connector nodes.
For more information, see Redeploying the container to 11.0.X.X.
Now, Netezza Performance Server can forward the log to a remote log server.