content_image/984494.jpg content_image/984495.jpg
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). 

<img src='content_image/984494.jpg'>

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. 

<img src='content_image/984495.jpg'>

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. 

