The graph of the JVM heap size on a data node shows that the value of 3GB Xmx/Xms and  6GB container memory was sufficient, as it maintained a steady maximum of around 2.3GB  (Figure 5-15). Checking the total memory consumed during this time period in Prometheus also shows  similar results, with the container memory peaking at around 4.5GB. See Figure 5-16. As the audit log generation uses Fluentd, data is sent directly to Elasticsearch, so there is no  need to consider Logstash. The client and master nodes generally stayed stable throughout the test. The sudden hike for  one of the client nodes in Figure 5-17 on page 179 is due to a new replica starting in advance  of enabling audit logging. Figure 5-16 Container memory usage with audit logging  Figure 5-15 JVM heap size 178  IBM Cloud Private System Administrator’s Guide