After AKS Node Restart - We have lost Disk Queue

Elastic Stack Beats
, ,
1

Hi Team,

Yesterday we have restarted our AKS Nodes and we have lost the disk queue. We see a new folder being created at AKS Node.

Here is the configuration file for filebeat:

volumeMounts:
- name: config
mountPath: /etc/filebeat.yml
readOnly: true
subPath: filebeat.yml
- name: data
mountPath: /usr/share/filebeat/data
- name: varlibdockercontainers
mountPath: /var/lib/docker/containers
readOnly: true
- name: varlog
mountPath: /var/log
readOnly: true
volumes:
- name: config
configMap:
defaultMode: 0600
name: filebeat-config
- name: varlibdockercontainers
hostPath:
path: /var/lib/docker/containers
- name: varlog
hostPath:
path: /var/log
# data folder stores a registry of read status for all files, so we don't send everything again on a Filebeat pod restart
- name: data
hostPath:
path: /var/lib/filebeat-data
type: DirectoryOrCreate

In order to retain the existing data/disk queue, is there a specific configuration we need to do in filebeat yaml?

As AKS node restart should not clear the disk queue and the data should be persistent even after AKS node restart.

2

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.