Filebeat log collection stops when the container is restarted

Elastic Stack Beats
1

We collect the logs of the container of Tomcat on Kubernetes with the container of Filebeat.
After restarting the Tomcat container, the log collection instance is updated, but the log collection instance is
It seems that log update is not detected and Filebeat log collection does not start. ..
Similarly, log collection for other apps will stop when you restart the container.

As a temporary measure, after restarting the application container, restart the file collection by restarting the Filebeat container.

When I checked the Filebeat log, there were no errors, so
I do not know the cause, and I am having trouble dealing with the root cause.

〇環境
Container on Kubernetes
Tomcat (log output is a persistent volume on Azure)
Filebeat

〇filebeat.yml

filebeat.inputs:

type: log
enabled: true
type: log
close_inactive: 5m
ignore_older: 15m
paths:

/var/lib/kubelet/plugins/kubernetes.io/azure-disk/mounts/m*/api.log
tags:
Tomcat_api.log

Is the setting wrong?
Is there any good solution?

2

Hey @Negi700,

It is difficult to know what can be happening there, a couple of ideas that come to mind now:

  • Filebeat has problems harvesting files from networked filesystems, because they not always report modifications as local disks do. Do you know if these azure disk behave like a normal disk, or as a networked disk (like NFS)?.
  • Tomcat truncates the log file when it starts, then Filebeat loses track of latest change. Do you know if tomcat writes to the same path after restart?

Could you share the kubernetes manifest of the Filebeat pod? This may help to identify some problem with the mounted volumes.

3

Hi @jsoriano.
Thank you for the reply.

No. I didn't know that NFS is deprecated.
I am making the log output to the persistent volume of Azure, but can this also be in NFS?

After restarting tomcat, the log was written to the same path.

Please check the kubernetes manifest as it will be posted later.

4

Posted kubernetes manifest.
Please confirm.

Chart.yaml

apiVersion: v1
appVersion: 20.01.01-sul
description: xxx system.
keywords:
- hitachi
- iot
- datalake
name: xxx-filebeat
version: 20.01.01-sul


values.yaml
namespace: "xxx"
filebeat:
  image: "xxxusa11macr101.azurecr.io/xxx/xxx-filebeat"
  imageTag: "19.10.01-sul"
  pullPolicy: Always
  name: xxx-filebeat
  ContainerPort: 5400
  service:
    name: "filebeat-service-front"
    type: ClusterIP
    port: 5400
  persistence:
    volumeName: kibana-log-volume
    storageSize: 30Gi
    storageClassName: managed-premium-resizale
  resources:
    requests:
      cpu: "1m"
      memory: "150Mi"
    limits:
      cpu: "300m"
      memory: "256Mi"
5 
filebeat-config-map.yaml

apiVersion: v1
kind: ConfigMap
metadata:
name: filebeat-config
namespace: "{{ .Values.namespace }}"
data:
filebeat.yml: |
###################### Filebeat Configuration Example #########################

# This file is an example configuration file highlighting only the most common
# options. The filebeat.reference.yml file from the same directory contains all the
# supported options with more comments. You can use it as a reference.
#
# You can find the full configuration reference here:
# https://www.elastic.co/guide/en/beats/filebeat/index.html

# For more available modules and options, please see the filebeat.reference.yml sample
# configuration file.

#=========================== Filebeat inputs =============================

filebeat.inputs:

# Each - is an input. Most options can be set at the input level, so
# you can use different inputs for various configurations.
# Below are the input specific configurations.

#- type: log

  # Change to true to enable this input configuration.
  #enabled: true

  # Paths that should be crawled and fetched. Glob based paths.
  #paths:
- type: log
  enabled: true
  
  close_inactive: 3m
  ignore_older: 3m
  paths:
    - /var/lib/kubelet/plugins/kubernetes.io/azure-disk/mounts/m*/access_log.*
  tags:
    - Apache_access_log
    
- type: log
  close_inactive: 3m
  ignore_older: 3m
  paths:
    - /var/lib/kubelet/plugins/kubernetes.io/azure-disk/mounts/m*/error_log.*
  tags:
    - Apache_error_log
    
- type: log
  close_inactive: 3m
  ignore_older: 3m
  paths:
    - /var/lib/kubelet/plugins/kubernetes.io/azure-disk/mounts/m*/xx-xxxx-api.log
  tags:
    - Tomcat_xx-xxxx-api.log

- type: log
  close_inactive: 3m
  ignore_older: 3m
  paths:
    - /var/lib/kubelet/plugins/kubernetes.io/azure-disk/mounts/m*/xx-xxxx-api-ext.log
  tags:
    - Tomcat_xx-xxxx-api-ext.log

- type: log
  close_inactive: 3m
  ignore_older: 3m
  paths:
    - /var/log/messages
  tags:
    - messages

- type: log
  close_inactive: 3m
  ignore_older: 3m
  paths:
    - /var/log/auth.log
  tags:
    - auth.log
        
    
  # Exclude lines. A list of regular expressions to match. It drops the lines that are
  # matching any regular expression from the list.
  #exclude_lines: ['^DBG']

  # Include lines. A list of regular expressions to match. It exports the lines that are
  # matching any regular expression from the list.
  #include_lines: ['^ERR', '^WARN']

  # Exclude files. A list of regular expressions to match. Filebeat drops the files that
  # are matching any regular expression from the list. By default, no files are dropped.
  #exclude_files: ['.gz$']

  # Optional additional fields. These fields can be freely picked
  # to add additional information to the crawled log files for filtering
  #fields:
  #  level: debug
  #  review: 1

  ### Multiline options

  # Multiline can be used for log messages spanning multiple lines. This is common
  # for Java Stack Traces or C-Line Continuation

  # The regexp Pattern that has to be matched. The example pattern matches all lines starting with [
  #multiline.pattern: ^\[

  # Defines if the pattern set under pattern should be negated or not. Default is false.
  #multiline.negate: false

  # Match can be set to "after" or "before". It is used to define if lines should be append to a pattern
  # that was (not) matched before or after or as long as a pattern is not matched based on negate.
  # Note: After is the equivalent to previous and before is the equivalent to to next in Logstash
  #multiline.match: after


#============================= Filebeat modules ===============================

filebeat.config.modules:
  # Glob pattern for configuration loading
  path: ${path.config}/modules.d/*.yml

  # Set to true to enable config reloading
  reload.enabled: false

  # Period on which files under path should be checked for changes
  #reload.period: 10s

#==========================  Modules configuration =============================
#filebeat.modules:

#-------------------------------- Apache Module --------------------------------
#- module: apache
#  access:
#    enabled: true
#    var.paths:
#      - "/var/lib/kubelet/plugins/kubernetes.io/azure-disk/mounts/m*/access_log.*"
#    tags: ["Apache_access_log"]
#    
#  error:
#    enabled: true
#    var.paths:
#      - "/var/lib/kubelet/plugins/kubernetes.io/azure-disk/mounts/m*/error_log.*"
#    tags: ["Apache_error_log"]
#
#==================== Elasticsearch template setting ==========================

setup.template.settings:
  #index.number_of_shards: 3
  #index.codec: best_compression
  #_source.enabled: false

#================================ General =====================================

# The name of the shipper that publishes the network data. It can be used to group
# all the transactions sent by a single shipper in the web interface.
#name:

# The tags of the shipper are included in their own field with each
# transaction published.
#tags: ["service-X", "web-tier"]

# Optional fields that you can specify to add additional information to the
# output.
#fields:
#  env: staging


#============================== Dashboards =====================================
# These settings control loading the sample dashboards to the Kibana index. Loading
# the dashboards is disabled by default and can be enabled either by setting the
# options here or by using the `setup` command.
#setup.dashboards.enabled: false

# The URL from where to download the dashboards archive. By default this URL
# has a value which is computed based on the Beat name and version. For released
# versions, this URL points to the dashboard archive on the artifacts.elastic.co
# website.
#setup.dashboards.url:

#============================== Kibana =====================================

# Starting with Beats version 6.0.0, the dashboards are loaded via the Kibana API.
# This requires a Kibana endpoint configuration.
setup.kibana:

  # Kibana Host
  # Scheme and port can be left out and will be set to the default (http and 5601)
  # In case you specify and additional path, the scheme is required: http://localhost:5601/path
  # IPv6 addresses should always be defined as: https://[2001:db8::1]:5601
  #host: "localhost:5601"

  # Kibana Space ID
  # ID of the Kibana Space into which the dashboards should be loaded. By default,
  # the Default Space will be used.
  #space.id:

#============================= Elastic Cloud ==================================

# These settings simplify using Filebeat with the Elastic Cloud (https://cloud.elastic.co/).

# The cloud.id setting overwrites the `output.elasticsearch.hosts` and
# `setup.kibana.host` options.
# You can find the `cloud.id` in the Elastic Cloud web UI.
#cloud.id:

# The cloud.auth setting overwrites the `output.elasticsearch.username` and
# `output.elasticsearch.password` settings. The format is `<user>:<pass>`.
#cloud.auth:

#================================ Outputs =====================================

# Configure what output to use when sending the data collected by the beat.

#-------------------------- Elasticsearch output ------------------------------
#output.elasticsearch:
  # Array of hosts to connect to.
  #hosts: ["monitoring-elasticsearch-service-front:9200"]

  # Optional protocol and basic auth credentials.
  #protocol: "https"
  #username: "elastic"
  #password: "changeme"

#----------------------------- Logstash output --------------------------------
output.logstash:
  # The Logstash hosts
  hosts: ["logstash-service-front:5044"]
  pipelining: 2
  
  # Optional SSL. By default is off.
  # List of root certificates for HTTPS server verifications
  #ssl.certificate_authorities: ["/etc/pki/root/ca.pem"]

  # Certificate for SSL client authentication
  #ssl.certificate: "/etc/pki/client/cert.pem"

  # Client Certificate Key
  #ssl.key: "/etc/pki/client/cert.key"

#================================ Processors =====================================

# Configure processors to enhance or manipulate events generated by the beat.

processors:
  - add_host_metadata: ~
  - add_cloud_metadata: ~

#================================ Logging =====================================

# Sets log level. The default log level is info.
# Available log levels are: error, warning, info, debug
#logging.level: debug

# At debug level, you can selectively enable logging only for some components.
# To enable all selectors use ["*"]. Examples of other selectors are "beat",
# "publish", "service".
#logging.selectors: ["*"]

logging.level: info
logging.to_files: true
logging.files:
  keepfiles: 14
  logging.files.interval: 24h
  path: /usr/local/filebeat/logs
  name: ${HOSTNAME}.log
  #name: ${HOSTNAME}.log.`date +%Y%m%d`
#logging.to_stderr: true
#logging.files.name: ${HOSTNAME}_filebeat
#logging.to_syslog: true

#============================== Xpack Monitoring ===============================
# filebeat can export internal metrics to a central Elasticsearch monitoring
# cluster.  This requires xpack monitoring to be enabled in Elasticsearch.  The
# reporting is disabled by default.

# Set to true to enable the monitoring reporter.
#monitoring.enabled: false

# Uncomment to send the metrics to Elasticsearch. Most settings from the
# Elasticsearch output are accepted here as well.
# Note that the settings should point to your Elasticsearch *monitoring* cluster.
# Any setting that is not set is automatically inherited from the Elasticsearch
# output configuration, so if you have the Elasticsearch output configured such
# that it is pointing to your Elasticsearch monitoring cluster, you can simply
# uncomment the following line.
#monitoring.elasticsearch:

#================================= Migration ==================================

# This allows to enable 6.7 migration aliases
#migration.6_to_7.enabled: true
#close_inactive: 1m

apache.yml: |
#========================== Modules configuration =============================
filebeat.modules:

#-------------------------------- Apache Module --------------------------------
- module: apache
  access:
    enabled: true
    var.paths:
      - "/var/lib/kubelet/plugins/kubernetes.io/azure-disk/mounts/m*/access_log.*"
    tags: ["Apache_access_log"]
    
  error:
    enabled: true
    var.paths:
      - "/var/lib/kubelet/plugins/kubernetes.io/azure-disk/mounts/m*/error_log.*"
    tags: ["Apache_error_log"]
6 
filebeat-daemonset.yaml

#apiVersion: apps/v1
#kind: StatefulSet
apiVersion: extensions/v1beta1
kind: DaemonSet
metadata:
  name: "{{ .Values.filebeat.name }}"
  namespace: "{{ .Values.namespace }}"
  labels:
    app.kubernetes.io/name: {{ include "app.name" . }}
    helm.sh/chart: {{ include "app.chart" . }}
    app.kubernetes.io/instance: {{ .Release.Name }}
    app.kubernetes.io/managed-by: {{ .Release.Service }}
spec:
  replicas: 4
  strategy:
    type: 
      rollingUpdate:
        maxUnavailable: 2
  selector:
    matchLabels:
      app.kubernetes.io/name: {{ include "app.name" . }}
      app.kubernetes.io/instance: {{ .Release.Name }}
      app: "{{ .Values.filebeat.name }}"
  template:
    metadata:
      labels:
        app.kubernetes.io/name: {{ include "app.name" . }}
        app.kubernetes.io/instance: {{ .Release.Name }}
        app: "{{ .Values.filebeat.name }}"
        name: "{{ .Values.filebeat.persistence.volumeName }}"
      annotations:
        security: "none"
    spec:
      containers:
      - name: filebeat
        image: "{{ .Values.filebeat.image }}:{{ .Values.filebeat.imageTag }}"
        imagePullPolicy: Always
        command: [ "/bin/sh","-c","filebeat modules enable apache ; filebeat -c /usr/local/filebeat/conf/filebeat.yml"]
        
        ports:
        - name: filebeat-http
          containerPort: 5044	

        {{- if .Values.filebeat.resources }}
        resources:
{{ toYaml .Values.filebeat.resources | indent 12 }}
        {{- end }}
        volumeMounts:
          - name: filebeat-config
            mountPath: /usr/local/filebeat/conf/filebeat.yml
            subPath: filebeat.yml
          - name: hostpath-messages
            mountPath: /var/log
          - name: hostpath-app-log-dir
            mountPath: /var/lib/kubelet/plugins/kubernetes.io/azure-disk/mounts
            readOnly: true
          - name: filebeat-apache-yml
            mountPath: /etc/filebeat/modules.d/apache.yml
            subPath: apache.yml
          - name: filebeat-log-dir
            mountPath: /usr/local/filebeat/logs
      volumes:
      - name: filebeat-config
        configMap:
          name: filebeat-config
          items:
          - key: filebeat.yml
            path: filebeat.yml
      - name: hostpath-messages
        hostPath:
          path: /var/log
          type: DirectoryOrCreate
      - name: hostpath-app-log-dir
        hostPath:
          path: /var/lib/kubelet/plugins/kubernetes.io/azure-disk/mounts
      - name: filebeat-apache-yml
        configMap:
          name: filebeat-config
          items:
          - key: apache.yml
            path: apache.yml
      - name: filebeat-log-dir
        hostPath:
          path: /usr/local/filebeat/logs
          type: DirectoryOrCreate    
  volumeClaimTemplates:
  - metadata:
      name: "{{ .Values.filebeat.persistence.volumeName }}"
      annotations:
        volume.beta.kubernetes.io/storage-class: "{{ .Values.filebeat.persistence.storageClassName }}"
    spec:
      accessModes: [ "ReadWriteOnce" ]
      resources:
        requests:
          storage: "{{ .Values.filebeat.persistence.storageSize }}"
7

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