Fine-Tuning Audit Data Delivery¶
Privacera PolicySync connectors send access audit events to the Audit Server in batches. Two settings control how those batches are formed and how large each event's request data can be. Tuning these values helps prevent HTTP 413 errors from the Audit Server and reduces the impact of high-volume audit streams.
If your environment generates high-volume audit streams or you observe HTTP 413 errors from the Audit Server, adjust these settings as described below.
These settings apply to all PolicySync connectors.
Configuration Properties¶
| Property | Description | Default Value |
|---|---|---|
| Audit Server Batch Size | Number of audit events sent to the Audit Server in a single batch. | 100 |
| Audit Request Data Max Characters | Maximum number of characters kept in the requestData field of each audit event. Events with longer request data are truncated before delivery to prevent HTTP 413 errors. | 4096 |
Setup¶
-
SSH to the instance where Privacera Manager is installed.
-
Open the connector variables file for editing:
Note
Replace
<connector-type>and<instance>with your connector type and instance name.Bash -
Add or update the following properties:
-
Apply the changes:
Step 1 - Setup which generates the helm charts. This step usually takes few minutes.
Step 2 - Apply the Privacera Manager helm charts. Step 3 - (Optional) Post-installation step which generates Plugin tar ball, updates Route 53 DNS and so on. This step is not required if you are updating only connector properties.
-
In the PrivaceraCloud portal, navigate to Settings → Applications.
-
On the Connected Applications screen, select your connector.
-
Select the pen icon or the Account Name to open the edit screen.
-
Go to Access Management → ADVANCED tab.
-
Under Add New Custom Properties, add the following:
-
Select SAVE to apply the changes.
- Prev topic: Advanced Configuration