viya4-monitoring-kubernetes icon indicating copy to clipboard operation
viya4-monitoring-kubernetes copied to clipboard

Published 20 hours ago • verified publisher icon sassoftware

Host path /var/log/v4m-fb-storage getting full

Open AbhissszZ opened this issue 6 months ago • 1 comments
trafficstars

As "v4m >> logging" uses Hostpath to store its logs, it was creating an issue where /var/log/v4m-fb-storage was getting full

  1. The customer was not happy to increase the disk space of Hostpath for the nodes.
  2. Even with the retention period of 1 day, the disk space was not enough.

So, I tried to find a way out that worked for me, I want to validate if the changes I made are acceptable.

changes done in one file was enough for v4m hostpath changefile name: [logging/fb/fluent-bit_helm_values_opensearch.yaml]

FROM

extraVolumes:

  • hostPath: path: /var/log/v4m-fb-storage type: DirectoryOrCreate name: v4m-fb-storage

TO

extraVolumes:

  • name: v4m-fb-storage nfs: server: <Nfs server hostname> path: /srv/nfs/v4m-fb-storage

Which worked! Even on the NFS Server, I could see "v4m logging" files getting created. I need to validate if this change does not affect anything else in v4m.

AbhissszZ avatar May 16 '25 12:05 AbhissszZ