Filebeat de inicio rápido

Filebeat de inicio rápido

Esta nota terminando en https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-installation.html , no sólo utilizan el estudio personal concluido.
herramienta de recopilación de registros Filebeat es ligero, a menudo con el uso del ELK, como la fuente de adquisición de datos para su uso.

Uso filebeat esquemática

Instalación y despliegue

Centos7 (usos autor)

Puesto que la descarga es demasiado lento, por lo que estoy aquí para salvar una versión descargada (filebeat-6.3.2-linux-x86_64.tar ), si usted utiliza su creación propia: https://quqi.gblhgk.com/s/1727102/ vafFOSOsw5AXKP3d

Cargado en el servidor, se puede extraer

deb (no probar):

    curl -L -O https://artifacts.elastic.co/downloads/beats/filebeat/filebeat-7.6.1-amd64.deb
    sudo dpkg -i filebeat-7.6.1-amd64.deb

rpm (no probar):

curl -L -O https://artifacts.elastic.co/downloads/beats/filebeat/filebeat-7.6.1-x86_64.rpm
sudo rpm -vi filebeat-7.6.1-x86_64.rpm

mac (no probar):

curl -L -O https://artifacts.elastic.co/downloads/beats/filebeat/filebeat-7.6.1-darwin-x86_64.tar.gz
tar xzvf filebeat-7.6.1-darwin-x86_64.tar.gz

Linux (no probar):

curl -L -O https://artifacts.elastic.co/downloads/beats/filebeat/filebeat-7.6.1-linux-x86_64.tar.gz
tar xzvf filebeat-7.6.1-linux-x86_64.tar.gz

Windows (no probar):

1. descargar https://download.elastic.co/beats/filebeat/filebeat-5.0.0-windows.zip

2. Descomprimir en C: \ Archivos de programa

3. Cambiar nombre de directorio filebeat-5.0.0-ventanas Filebeat

4. PowerShell botón derecho del ratón en el icono y seleccione "Ejecutar como administrador"

5. Ejecute el siguiente comando para instalar el servicio Windows Filebeat:

    PS > cd 'C:\Program Files\Filebeat'
    PS C:\Program Files\Filebeat> .\install-service-filebeat.ps1

Tenga en cuenta que
puede requerir subvención adicional permisos de ejecución. Comando es:PowerShell.exe -ExecutionPolicy RemoteSigned -File .\install-service-filebeat.ps1

rápido

Sobre el medio ambiente: centos7, JDK8, filebeat-6.3.2, 6.5.1-logstash

filebeat.yml 配置

Filebeat.yml modificar el archivo de configuración, el nodo principal cambio [filebeat.inputs, trayectorias, include_lines, nombre, (output.logstash)]

Modificar, según sea necesario, necesito escuchar aquí para configurar la carpeta filebeat [/ shaofei / logs] bajo el sufijo [.log], la clave está escuchando [ 'excepción', 'inicio de sesión de usuario anormal'],
Nota: Si es necesario escuchar chino, hay que asegurarse de que el archivo está codificado como UTF-8. O el uso [] para especificar el archivo de codificación que codifica el monitor
me nombre configurado: a "study128", que se utiliza aquí Logstash como su salida] [Logstash de salida, incluso si el registro de salida para recibir filebeat no extremo receptor no afectará filebeat empezar a
modificar el fichero de configuración debe prestar atención formato 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:
    - /filebeat/testlogs/input/*.log 
  include_lines: ['Exception','用户登录异常']
    #- c:\programdata\elasticsearch\logs\*
  #encoding: gbk
  # 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

  # Mutiline 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
  
multiline:
 tail_files: true

#============================= 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: "study128"

# 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` CLI flag or 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"

#============================= 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: ["localhost:9200"]

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

#----------------------------- Logstash output --------------------------------
output.logstash:
  # The Logstash hosts
  hosts: ["127.0.0.1:10515"]

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

#================================ 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: ["*"]

#============================== 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.
#xpack.monitoring.enabled: false

# Uncomment to send the metrics to Elasticsearch. Most settings from the
# Elasticsearch output are accepted here as well. Any setting that is not set is
# automatically inherited from the Elasticsearch output configuration, so if you
# have the Elasticsearch output configured, you can simply uncomment the
# following line.
#xpack.monitoring.elasticsearch:
#scan_frequency: 30s
#----------------------------- kafka output --------------------------------  
#output.kafka:
#  enabled: true
#  hosts: ["132.228.248.201:9092","132.228.248.202:9092","132.228.248.203:9092"]
#  topic: ETE_CBA_ZZQS_LOG_ERROR
#  version: 0.10.0.1

Inicio filebeat

./filebeat -e -c filebeat.yml -d "publish"

Dado que la filebeat.ymlque se da inicio, permiso para realizar la modificación filebeat.yml (se puede utilizar el comando de sus recomendaciones)

comienzo exitoso

Nota: Para garantizar la configuración de ruta filebeat.yml adquisición es tener permisos de lectura!

Prueba si la adquisición exitosa

1. Crear un registro de la prueba en el directorio especificado

echo "
    2020-03-27 16:51:25,422 ERROR com.quxuecx.Start ->net.sf.json.JSONException: JSONObject["matchID"] not found.
    2020-03-27 16:51:25,422 ERROR com.quxuecx.Start ->net.sf.json.JSONException: JSONObject["matchID"] not found.
    2020-03-27 16:51:25,422 ERROR com.quxuecx.Start ->net.sf.json.JSONException: JSONObject["matchID"] not found.
">>b.log

2. éxito

Nota: Si no ve el éxito de la foto fue tomada, y comprueba los perfiles y permisos filebeat.yml escuchas cuidadosamente si la ruta y el archivo se puede leer.
Nota: Los contenidos del archivo, debe iniciar sesión formato de registro e incluir las palabras clave que está escuchando, por favor.

prueba de acoplamiento Logstash

Especial atención: filebeat.yml configurado en output.logstash: hosts: ["127.0.0.1:10515"]la que este puerto a 10515 y el perfil logstash input filebeatpuerto consistente.

Ver la información general de logstash >> https://blog.csdn.net/pyfysf/article/details/100942174

perfil log_error.conf logstash

input {
    # 配置filebeat
    beats {
        port => 10515
    }
}

filter {

}

output {

    # 配置输出到文件中
    file{
       path=>"/home/shaofei/output.log"
    }

    #配置输出到控制台
	stdout{
		codec=>rubydebug
	}
}

Inicio logstash

./bin/logstash -rf ./config/log_error.conf

log_error.conf perfil

input {
    # 配置filebeat
    beats {
        port => 10515
    }
}

filter {

}

output {

    # 配置输出到文件中
    file{
       path=>"/home/shaofei/output.log"
    }

    #配置输出到控制台
	stdout{
		codec=>rubydebug
	}
}

Inicio logstash

./bin/logstash -rf ./config/log_error.conf