# Problem with filebeat or Kibana?

**URL:** <https://discuss.elastic.co/t/problem-with-filebeat-or-kibana/317514>\
**Category:** Kibana\
**Created:** [October 26, 2022, 12:08pm UTC](https://discuss.elastic.co/t/problem-with-filebeat-or-kibana/317514 "2022-10-26T12:08:17Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![kikinous](https://avatars.discourse-cdn.com/v4/letter/k/6de8d8/32.png) [@kikinous](https://discuss.elastic.co/u/kikinous)\
**Post date:** [October 26, 2022, 12:08pm UTC](https://discuss.elastic.co/t/problem-with-filebeat-or-kibana/317514/1 "2022-10-26T12:08:17Z")

</div>

hello,

We have a problem with our ELK cluster. Logs retrieved by filebeat on our application servers are not completely displayed at the Kibana level.

We don't know if it's a log injection problem in ELK or if it's a display problem in Kibana.

We have a large and redundant infrastructure

We have 3 ELK Data, 3 elk Master. 2 indexer logstash with a REDIS broker, 2 front-end logstash and 1 kibana.

beat agent is filebeat which retrieves our logs from the application servers. Then sends to the 2 front end logstash in loadbalancing mode. Each frontend logstash sends the frame to a dedicated REDIS.

The logstash indexer takes over to format log line via GROK, then send to the ELK master.

our version is 7.17.x on all ELK components.

We are sending acces.log via the filestream “odm-filestream-access”, and the yellow lines do not seem to be visible in Kibana via discover.

###################### 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:

# [Filebeat Reference | Elastic](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 pour ODM by KSA===============================

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.

# filestream is an input for collecting log messages from files.

- type: filestream  
id: odm-filestream-access

#filestream is an input for collecting log messages from files.

- type: filestream  
id: odm-filestream-server

#filestream is an input for collecting log messages from files.

- type: filestream  
id: odm-filestream-odmtarif

#filestream is an input for collecting log messages from files.

- type: filestream  
id: odm-filestream-odmanafact

# filestream is an input for collecting log messages from files.

- type: filestream  
id: odm-filestream-odmperformances

# ============================== 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

# ======================= 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](http://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](http://localhost:5601/path)

# IPv6 addresses should always be defined as: https://[2001:db8::1]:5601

host: "150001l1it.cen.ramage: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/](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: ["localhost:9200"]

# Protocol - either `http` (default) or `https`.

#protocol: "https"

# Authentication credentials - either API key or username/password.

#api\_key: "id:api\_key"  
#username: "elastic"  
#password: "changeme"

# ------------------------------ Logstash Output -------------------------------

output.logstash:

# The Logstash hosts

hosts: ["150001l1ipa.cen.ramage:5044","150001l1ipb.cen.ramage:5044"]  
timeout: 60  
worker: 4  
loadbalance: true

# 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 =================================

processors:

- add\_host\_metadata:  
when.not.contains.tags: forwarded
- add\_cloud\_metadata: ~
- add\_docker\_metadata: ~
- add\_kubernetes\_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",

# "publisher", "service".

#logging.selectors: ["\*"]

# ============================= X-Pack 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

# Sets the UUID of the Elasticsearch cluster under which monitoring data for this

# Filebeat instance will appear in the Stack Monitoring UI. If output.elasticsearch

# is enabled, the UUID is derived from the Elasticsearch cluster referenced by output.elasticsearch.

#monitoring.cluster\_uuid:

# 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:

# ============================== Instrumentation ===============================

# Instrumentation support for the filebeat.

#instrumentation:  
# Set to true to enable instrumentation of filebeat.  
#enabled: false

```
# Environment in which filebeat is running on (eg: staging, production, etc.)
#environment: ""

# APM Server hosts to report instrumentation results to.
#hosts:
# - http://localhost:8200

# API Key for the APM Server(s).
# If api_key is set then secret_token will be ignored.
#api_key:

# Secret token for the APM Server(s).
#secret_token:

```

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

# This allows to enable 6.7 migration aliases

#migration.6\_to\_7.enabled: true

Thanks for your support !

 ![log view](https://us1.discourse-cdn.com/elastic/original/3X/9/f/9f3c993550192251b968cf3c9d6a7c0a8d482523.jpeg)  
 ![kibana view](https://us1.discourse-cdn.com/elastic/original/3X/5/e/5e90fdaa74502f2aa0311bf75e4baaf7f73e0d8f.jpeg)

* * *

1. 0-9 

2. 0-9 

3. 0-9

---

<div class="post-metadata">

**Author:** ![kikinous](https://avatars.discourse-cdn.com/v4/letter/k/6de8d8/32.png) [@kikinous](https://discuss.elastic.co/u/kikinous)\
**Post date:** [October 26, 2022, 1:13pm UTC](https://discuss.elastic.co/t/problem-with-filebeat-or-kibana/317514/2 "2022-10-26T13:13:49Z")

</div>

After lot of test, redis 6.2.4 or 5.2.8 seems to be the problem !

we bypass it , and send all log to the logstash indexer.

---

<div class="post-metadata">

**Author:** ![kikinous](https://avatars.discourse-cdn.com/v4/letter/k/6de8d8/32.png) [@kikinous](https://discuss.elastic.co/u/kikinous)\
**Post date:** [October 26, 2022, 1:33pm UTC](https://discuss.elastic.co/t/problem-with-filebeat-or-kibana/317514/3 "2022-10-26T13:33:55Z")

</div>

If anyone find the error in our REDIS config , please advise me . cordially

################################## CONFIG KSA ###################################

################################## NETWORK #####################################  
bind 0.0.0.0  
protected-mode yes  
port 6379

# TCP listen() backlog.

# 

tcp-backlog 511

# Unix socket.

# 

# Close the connection after a client is idle for N seconds (0 to disable)

timeout 0

# TCP keepalive.

# 

# A reasonable value for this option is 300 seconds, which is the new

# Redis default starting with Redis 3.2.1.

tcp-keepalive 300

################################# GENERAL #####################################  
daemonize no  
supervised no  
pidfile /var/run/redis\_6379.pid  
loglevel notice  
logfile "/tools/redis/logs/redis.log"  
databases 16  
always-show-logo yes

################################ SNAPSHOTTING ################################  
save 900 1  
save 300 10  
save 60 10000  
stop-writes-on-bgsave-error yes  
rdbcompression yes  
rdbchecksum yes

# The filename where to dump the DB

# 

dbfilename meteore-dump.rdb

# The working directory.

# 

dir /tools/redis/data/

################################# REPLICATION #################################

slave-serve-stale-data yes  
slave-read-only yes  
repl-diskless-sync no  
repl-diskless-sync-delay 5  
repl-disable-tcp-nodelay no  
slave-priority 100

################################## SECURITY ###################################

requirepass xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

############################## MEMORY MANAGEMENT ################################  
maxmemory 2000mb  
maxmemory-policy allkeys-lru

############################# LAZY FREEING ####################################

lazyfree-lazy-eviction no  
lazyfree-lazy-expire no  
lazyfree-lazy-server-del no  
slave-lazy-flush no

############################## APPEND ONLY MODE ###############################  
appendonly yes  
appendfilename "appendonly.aof"  
appendfsync everysec  
no-appendfsync-on-rewrite no  
auto-aof-rewrite-percentage 100  
auto-aof-rewrite-min-size 64mb  
aof-load-truncated yes  
aof-use-rdb-preamble no

################################ LUA SCRIPTING ###############################  
lua-time-limit 5000

################################## SLOW LOG ###################################  
slowlog-log-slower-than 10000  
slowlog-max-len 1280

################################ LATENCY MONITOR ##############################  
latency-monitor-threshold 0

############################# EVENT NOTIFICATION ##############################  
notify-keyspace-events ""

############################### ADVANCED CONFIG ###############################  
hash-max-ziplist-entries 512  
hash-max-ziplist-value 64  
list-max-ziplist-size -2  
list-compress-depth 0  
set-max-intset-entries 512  
zset-max-ziplist-entries 128  
zset-max-ziplist-value 64  
hll-sparse-max-bytes 3000  
activerehashing yes

client-output-buffer-limit normal 0 0 0  
client-output-buffer-limit slave 256mb 64mb 60  
client-output-buffer-limit pubsub 32mb 8mb 60

hz 10

aof-rewrite-incremental-fsync yes

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [November 23, 2022, 1:34pm UTC](https://discuss.elastic.co/t/problem-with-filebeat-or-kibana/317514/4 "2022-11-23T13:34:39Z")

</div>

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