Manips to update the Discover board

Good morning,

Actually, I use grok pipeline in Elasticsearch but it doesn't seem that the modifications apply when I change something on my pipeline. What are the manipulations to do to see them ?

Regards.

if you share, how you update the pipeline, that getting the pipelines shows that has changed and a provide a fully reproducible example, this would help a lot.

Also, the Elasticsearch version in place would help.

Thank you!

I update the pipeline by restarting Elasticsearch, Filebeat and Kibana.

Do you want the pipeline ?

Thank you to you.

Restarting Elasticsearch or Kibana has nothing to do with updating a pipeline. Are you referring to the filebeat which is supposed to store the pipeline? Or does it get overwritten? Or is it a fully seperate pipeline?

Some more context would be helpful.

The pipeline gets overwritten by adding filebeat.overwrite_pipelines: true in /etc/filebeat/filebeat.yml.

I also tried to do filebeat setup --pipelines but it doesn't seem to change anything.
I work with a pipeline I created.

if you delete the pipeline on the elasticsearch side, does it get created, but still is the old one?

Also, can you share. you full filebeat configuration, plus the pipeline in order to be able to reproduce? Plus the logs, when running filebeat -e run -v?

Also, the version of filebeat would help.

Note: I moved this to the beats forum, as this does not seem like an Elasticsearch problem to me.

The default ones are still presents, even if I delete the one I make (or I didn't understand).

The Filebeat config :

###################### 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.overwrite_pipelines: true

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:
    - /data/logs/network/*/*.log 
    # - /var/log/*.log
    #- c:\programdata\elasticsearch\logs\*

  # 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

#==================== Elasticsearch template setting ==========================

setup.template.settings:
  index.number_of_shards: 1
  #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: "x.x.x.x:5601"
    protocol: "https"
    username: "secret"
    password: "secret"
    
    ssl.verification_mode: none
 
 # 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: ["x.x.x.x:9200"]

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

  # Authentication credentials - either API key or username/password.
  #api_key: "id:api_key"
  username: "secret"
  password: "secret"

  ssl.verification_mode: none
  #pipeline: logs_pipeline

  #setup.template.overwrite: true
#----------------------------- Logstash output --------------------------------
#output.logstash:
  # The Logstash hosts
  #hosts: ["localhost:5044"]

  # 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: ~
  - 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",
# "publish", "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:

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

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

For the command, the results :

2020-03-16T17:22:41.356+0100    INFO    instance/beat.go:622    Home path: [/usr/share/filebeat] Config path: [/etc/filebeat] Data path: [/var/lib/filebeat] Logs path: [/var/log/filebeat]
2020-03-16T17:22:41.356+0100    INFO    instance/beat.go:630    Beat ID: fdbb419a-8d26-43db-abdb-02debc9e97f8
2020-03-16T17:22:41.361+0100    INFO    instance/beat.go:380    filebeat stopped.
2020-03-16T17:22:41.361+0100    ERROR   instance/beat.go:933    Exiting: data path already locked by another beat
Exiting: data path already locked by another beat

And the pipeline :

PUT /_ingest/pipeline/logs_pipeline
{
  "description": "Pipeline for parsing bgp messages.",
  "processors": [
    {
      "grok": {
        "pattern_definitions" : {
            "GREEDYMULTILINE" : """(.|
)*""",
            "HANDLE_STATE": "bgp_handle_notify", 
            "IFACHANGE_STATE": "bgp_ifachange_group",
            "CLOSE_SESSION": "BGP_IO_ERROR_CLOSE_SESSION",
            "SEND_SESSION": "bgp_send",
            "SPECIAL_CHAR": ":",
            "TEST": ".*? ([0-9]?) .*"
          },
        "ignore_missing": true,
        "trace_match": true,
        "field": "message",
        "patterns": [
            /* BGP */
            "(?:%{SYSLOGTIMESTAMP:system.syslog.timestamp}|%{TIMESTAMP_ISO8601:system.syslog.timestamp})? %{SYSLOGHOST:host.hostname} %{DATA:process.name}(?:\\[%{POSINT:process.pid:long}\\])?: %{DATA:bgp.state}: %{DATA:bgp.protocol} %{IP:client.ip} \\(%{DATA:bgp.as}\\) %{GREEDYDATA:system.syslog.message}",
            
            /* STANDARD */
            "(?:%{SYSLOGTIMESTAMP:system.syslog.timestamp}|%{TIMESTAMP_ISO8601:system.syslog.timestamp})? %{SYSLOGHOST:host.hostname} %{DATA:process.name}(?:\\[%{POSINT:process.pid:long}\\])?: %{GREEDYMULTILINE:system.syslog.message}",
            "(?:%{SYSLOGTIMESTAMP:system.syslog.timestamp}|%{TIMESTAMP_ISO8601:system.syslog.timestamp})? %{GREEDYMULTILINE:system.syslog.message}"
        ]
      }
    },
    {
      "remove": {
        "field": "message"
      }
    },
    {
      "rename": {
        "field": "system.syslog.message",
        "target_field": "message",
        "ignore_missing": true
      }
    },
    {
      "date": {
        "formats": [
          "MMM  d HH:mm:ss",
          "MMM dd HH:mm:ss",
          "MMM d HH:mm:ss",
          "ISO8601"
        ],
        "on_failure": [
          {
            "append": {
              "field": "error.message",
              "value": "{{ _ingest.on_failure_message }}"
            }
          }
        ],
        "if": "ctx.event?.timezone == null",
        "field": "system.syslog.timestamp",
        "target_field": "@timestamp"
      }
    },
    {
      "date": {
        "if": "ctx.event?.timezone != null",
        "field": "system.syslog.timestamp",
        "target_field": "@timestamp",
        "formats": [
          "MMM  d HH:mm:ss",
          "MMM dd HH:mm:ss",
          "MMM d HH:mm:ss",
          "ISO8601"
        ],
        "timezone": "{{ event.timezone }}",
        "on_failure": [
          {
            "append": {
              "field": "error.message",
              "value": "{{ _ingest.on_failure_message }}"
            }
          }
        ]
      }
    },
    {
      "remove": {
        "field": "system.syslog.timestamp"
      }
    }
  ],
  "on_failure": [
    {
      "set": {
        "field": "error.message",
        "value": "{{ _ingest.on_failure_message }}"
      }
    }
  ]
}

I am in filebeat-7.6.0

With filebeat -e run -v, I have an error but I don't know what run where.

How can I fix it ?

Couple of things.

First, you should run that filebeat command only, when no other instance is running.

Second, if you changed the pipeline via the API, then you should set overwrite_pipelines to false to ensure that filebeat does not overwrite it.

Third, you have commented out the use of any pipeline in your filebeat output.

So first, I made the changes on the .yml.

After I did service filebeat stop and filebeat -e run -v and it returns
ERROR pipeline/output.go:100 Failed to connect to backoff(elasticsearch(https://x.x.x.x:9200)): Connection marked as failed because the onConnect callback failed: cannot retrieve the elasticsearch license from the /_xpack endpoint, Filebeat requires the default distribution of Elasticsearch. Please make the endpoint accessible to Filebeat so it can verify the license.: could not retrieve the license information from the cluster: 503 Service Unavailable: {"error":{"root_cause":[{"type":"master_not_discovered_exception","reason":null}],"type":"master_not_discovered_exception","reason":null},"status":503}

It becomes confusing for me. Do you know what is happening ?

Have you tried to install filebeat in the oss distribution but run Elasticsearch in the default distribution? Can you shed some light which versions/distributions (or just files) you downloaded?

Erm, I hope I don't answer wrong. Elasticsearch, Kibana and Filebeat are in 7.6.0. On a server are Kibana and Elasticsearch, on another is Filebeat for the logs.

I install all three with this way : https://www.elastic.co/guide/en/kibana/current/deb.html

Sorry if my answer doesn't help.

This is not everything, as basically there are two flavors for each version. The basic one and the OSS distribution. Can you check the names of the files you downloaded and share?

Where can I find them ?
And what is the OSS distribution ?

Please share which link you used to download elasticsearch/kibana/filebeat. Thank you.

Kibana : https://www.elastic.co/guide/en/kibana/current/deb.html#deb-key
Elasticsearch : https://www.elastic.co/guide/en/elasticsearch/reference/current/deb.html#deb-key
Filebeat : https://www.elastic.co/guide/en/beats/filebeat/current/setup-repositories.html#_apt

This is not the exact download link of the debian package. please provide those.

Kibana : https://www.elastic.co/guide/en/kibana/current/deb.html
Elasticsearch : https://www.elastic.co/guide/en/elasticsearch/reference/current/deb.html
These ones ?