Linux-UNIX: Increasing S-TAP and K-TAP throughput with dynamic ring buffers

By default, each sqlguard data connection is associated with one S-TAP buffer. The sqlguard thread reads data from the S-TAP buffer and sends it to collector. Enable dynamic ring buffers to add S-TAP buffers to each main sqlguard data connection, and prevent an overflow in the S-TAP buffer during traffic peaks.

About this task

When a ring buffer becomes full, Guardium allocates a new buffer, and all data that is captured from the K-TAP is written to the newly created buffer. The sqlguard thread always reads from the first created buffer and sends data to sqlguard. When a buffer is empty and another ring buffer is already created, the empty buffer is deleted. Guardium manages the dynamic ring buffers without user intervention: when, and how many, ring buffers to allocate, or close, per main connection. The maximum number of ring buffers is 10. If the S-TAP fails over, data in all buffers is moved to the new buffers.

Procedure