You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Logstash version: 7.16.0 (running on Raspberry Pi 4 Model B Rev 1.1 with AArch64 [ARM64] using Ubuntu 20.04 LTS)
Logstash installation source: APT
How is Logstash being run: As a service using systemd
How was the Logstash Plugin installed: Default plugin
JVM:
openjdk version "11.0.13" 2021-10-19
OpenJDK Runtime Environment Temurin-11.0.13+8 (build 11.0.13+8)
OpenJDK 64-Bit Server VM Temurin-11.0.13+8 (build 11.0.13+8, mixed mode)
OS version: Ubuntu 20.04 LTS (5.4.0-1047-raspi #52-Ubuntu SMP PREEMPT Wed Nov 24 08:16:38 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux)
Description of the problem including expected versus actual behavior:
Expected: Input data should go its respective index
Error: Data from one pipeline which has a specific index is also going to another index. (two copies being created)
There are two different instances of Filebeat running on a single host. Both have different installation and configuration mechanisms.
Input is via filebeat:
Installation and persistence:
Filebeat installed via APT (running configuration: /etc/filebeat/filebeat.yml) && referred to as cowrie-*
Filebeat unzipped and made persistent via /etc/rc.local (running configuration: /home/user/filebeat2/filebeat.yml) && referred to as cowrie-firewall-*
Configuration:
Both filebeat instances have their unique configurations. They are configured to send logs to Logstash on different ports
Logstash
Logstash is running on a single host with different pipelines for each ingest.
Logs being sent to pipeline "cowrie-" on port 5045 are visible in the index of pipeline "cowrie-logstash-" (pipeline.id: honeypot_ingest)
Logs being sent to pipeline "cowrie-firewall*" on port 5055 are visible in the index of pipeline "cowrie-logstash-*" (pipeline.id: cowrie_firewall_ingest)
Output section of the configuration for each configuration:
A. cowrie-*
input {
# filebeats
beats {
port => 5054
type => "cowrie"
#id => "honeypot_ingest"
}
Verify input configuration of each filebeat instance:
A. cowrie-logstash-* (filepath: /etc/filebeat/filebeat.yml)
# Paths that should be crawled and fetched. Glob based paths.
paths:
#- /var/log/*.log
- /srv/cowrie/var/log/cowrie/*.json
- /home/ubuntu/logs/*.json
#- c:\programdata\elasticsearch\logs\*
B. Cowrie-firewall-* (filepath: /home/user/filebeat2/filebeat.yml)
# Paths that should be crawled and fetched. Glob based paths.
paths:
#- /var/log/*.log
- /var/log/dshield.log
#- /home/ubuntu/logs/*.json
#- c:\programdata\elasticsearch\logs\*
Verify output configurations for filebeat:
A. cowrie-logstash-* (filepath: /etc/filebeat/filebeat.yml)
output.logstash:
# The Logstash hosts
#hosts: ["localhost:5044"]
hosts: ["IP REDACTED:5054"]
B. Cowrie-firewall-* (filepath: /home/user/filebeat2/filebeat.yml)
output.logstash:
# The Logstash hosts
#hosts: ["localhost:5044"]
hosts: ["IP REDACTED:5055"]
Provide logs (if relevant):
I can email the logs if need be.
Logstash information:
Please include the following information:
JVM:
openjdk version "11.0.13" 2021-10-19
OpenJDK Runtime Environment Temurin-11.0.13+8 (build 11.0.13+8)
OpenJDK 64-Bit Server VM Temurin-11.0.13+8 (build 11.0.13+8, mixed mode)
OS version: Ubuntu 20.04 LTS (5.4.0-1047-raspi #52-Ubuntu SMP PREEMPT Wed Nov 24 08:16:38 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux)
Description of the problem including expected versus actual behavior:
Expected: Input data should go its respective index
Error: Data from one pipeline which has a specific index is also going to another index. (two copies being created)
There are two different instances of Filebeat running on a single host. Both have different installation and configuration mechanisms.
Input is via filebeat:
Installation and persistence:
Configuration:
Logstash
A. cowrie-*
B. Cowrie-Firewall-*
pipelines.yml
Steps to reproduce:
A. cowrie-logstash-* (filepath: /etc/filebeat/filebeat.yml)
B. Cowrie-firewall-* (filepath: /home/user/filebeat2/filebeat.yml)
A. cowrie-logstash-* (filepath: /etc/filebeat/filebeat.yml)
B. Cowrie-firewall-* (filepath: /home/user/filebeat2/filebeat.yml)
Provide logs (if relevant):
I can email the logs if need be.
Please refer to the thread: https://discuss.elastic.co/t/logstash-ingest-pipeline-data-from-one-pipeline-going-to-another/289131
The text was updated successfully, but these errors were encountered: