Adjusting Guardium central manager and OpenShift Container Platform settings for data mart streaming

This topic describes settings that you can configure to avoid problems or delays when streaming to Guardium Insights.

Adjust OpenShift load balancer settings

If your OpenShift Container Platform employs a load balancer, you will need to adjust its settings to properly route traffic to Guardium Insights. For example, if you use a High Availability Proxy (HAProxy) load balancer, you will need to define a frontend and backend to enable data mart streaming by adding settings similar to these:

frontend sshd
 bind *:<port_number>
 default_backend ssh
 timeout client 1h

backend ssh
 mode tcp
 server worker0 10.16.38.62:<port_number>
 server worker1 10.16.46.74:<port_number>
 server worker2 10.16.50.102:<port_number>
 server worker3 10.16.50.179:<port_number>
 server worker4 10.16.51.116:<port_number>
 server worker5 10.16.51.117:<port_number>
 server worker6 10.16.51.146:<port_number>
 server worker7 10.16.53.241:<port_number>
 server worker8 10.16.53.249:<port_number>

Where <port_number> is the port that the frontend listens on. This port number is dynamically-allocated for communication between Guardium Data Protection and Guardium Insights, and it is described in Port requirements (this topic includes instructions for determining the port).

Managing the Guardium central manager user synchronization setting to avoid delays

After configuring data mart from Guardium Insights, it will take 1 to 2 hours for data related information to start showing up in Guardium Insights.