Despite the bootstrap graphman bundle has set audit.sink.alwaysSaveInternal=false this setting is still set to true after bootstrapping the pod .

Products

• CA API Gateway

Issue/Introduction

When using a graphman bundle to bootstrap a gateway pod or appliance version 11.1.2  this setting is still set to true in policy manager audit config  after bootstrapping the pod . 

This could result into heap space issue when the pod is writing audit data to the epheremal in memory database.

Resolution

In gateway 11.1.1 with schema version 11.1.1 this was set from the folllowing  cwp .

{
      "goid": "bc9d2eef6b1db15cb9c4d6456feec269",
      "name": "audit.sink.alwaysSaveInternal",
      "checksum": "dd7aee2a665b9245a9c6ca500ab36539a06fcf42",
      "description": "If true, audit records will always be saved to the internal database, even if they were successfully processed via a configured audit sink policy. (default=false)",
      "hiddenProperty": true,
      "value": "false"
    },

With gateway 11.1.2 and graphman schema 11.1.2 this is now included in the audit config . 

The default for this setting is "true"  if the setting is not there , so in this case the bundle was created with a 11.1.1 schema and did not include the setting , which is causing to have this enabled by default when imported on a 11.1.2 gateway. 

make sure the bundle used contains the following information for the audit config 

  "auditConfigurations": [
    {
      "goid": "00000000000000040000000000000001",
      "name": "AuditConfig",
      "checksum": "679034b73149c328c0af8fb7016036bb36ade31a",

      "alwaysSaveInternal": false,
      "lookupPolicyName": "[Internal Audit Lookup Policy]",
      "sinkPolicyName": "[Internal Audit Sink Policy]"
    }