# Download new version of filebeat

**URL:** <https://discuss.elastic.co/t/download-new-version-of-filebeat/241607>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [July 17, 2020, 8:21am UTC](https://discuss.elastic.co/t/download-new-version-of-filebeat/241607 "2020-07-17T08:21:10Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![JoseSaborido](https://avatars.discourse-cdn.com/v4/letter/j/9de0a6/32.png) [@JoseSaborido](https://discuss.elastic.co/u/JoseSaborido)\
**Post date:** [July 17, 2020, 8:21am UTC](https://discuss.elastic.co/t/download-new-version-of-filebeat/241607/1 "2020-07-17T08:21:10Z")

</div>

Hi!

I've been trying to configure filebeat to create an index every day but it seems to be impossible. I have seen this issue [https://github.com/elastic/beats/issues/11595](https://github.com/elastic/beats/issues/11595)

So I have been trying to download the version 8 alpha or snapshot of filebeat but I can't find it anywhere is not in the official artifacts or in GitHub  
[https://www.elastic.co/es/downloads/past-releases#filebeat](https://www.elastic.co/es/downloads/past-releases#filebeat)

> **[Releases · elastic/beats](https://github.com/elastic/beats/releases)**
>
> :tropical\_fish: Beats - Lightweight shippers for Elasticsearch & Logstash - elastic/beats

Where can I download the 8 version of filebeat?

Thanks,  
Jose

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [July 21, 2020, 12:15am UTC](https://discuss.elastic.co/t/download-new-version-of-filebeat/241607/2 "2020-07-21T00:15:00Z")

</div>

Welcome to our community! 😃

> [@JoseSaborido](#):
>
> I've been trying to configure filebeat to create an index every day but it seems to be impossible

It sounds like this should be a fixable issue, rather than just moving to a snapshot build.

Can you share what problems you are having, your configs, any errors etc.

---

<div class="post-metadata">

**Author:** ![JoseSaborido](https://avatars.discourse-cdn.com/v4/letter/j/9de0a6/32.png) [@JoseSaborido](https://discuss.elastic.co/u/JoseSaborido)\
**Post date:** [July 21, 2020, 8:08am UTC](https://discuss.elastic.co/t/download-new-version-of-filebeat/241607/3 "2020-07-21T08:08:47Z")

</div>

Hi thanks 🙂

Ok I'll describe the problem. I have an elastic cluster dockerized in a server with version 7.4.2. I other servers I have filebeat installed I read that by default the filebeat rotate the index using ILM and generates a index every day but it only creates one index with the date if there is not another created. I want a list of index with one created every day. This is the config:

```auto
    ###################### 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: false

      # Paths that should be crawled and fetched. Glob based paths.
      paths:
    - /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: "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: ["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: ["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: error

    # 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

    setup.ilm.enabled: auto
    setup.ilm.rollover_alias: "filebeat-%{[agent.version]}"
    setup.ilm.pattern: "{now/d}-000001"

```

I added the ilm settings at the end but I still have the first index created and it does not rotate everyday:

```auto
    health status index uuid pri rep docs.count docs.deleted store.size pri.store.size
    green open filebeat-7.8.0-2020.07.16-000001 5Au5pyNyQv-Zwh0bqcZJvA 1 1 14535 0 17.4mb 8.7mb
    green open auditbeat-7.4.2-2020.07.01-000001 S_QKJE90R7eo79TZGK2j4A 1 1 83607 0 93.4mb 46.7mb
    green open filebeat-7.4.2-2020.07.01-000001 ANqF4ia1RZuqVxDWJgFP2Q 1 1 3886543 0 2gb 1gb
    green open .kibana_task_manager_1 wJO_avJRTp6uhlARdrXlIg 1 1 2 0 64.7kb 32.3kb
    green open .apm-agent-configuration C18grt79Qeu1lsMVqDBgqA 1 1 0 0 566b 283b
    green open .kibana_1 mlgR3OLGTpKUzFYqWFAWKw 1 1 1350 13 1.2mb 701.5kb

```

P.D: I'm really sending the logs to a server not localhost, but I have to hide in the config shown in order to keep confidentiality. Anyways maybe there is a change I have to do in elastic and not in filebeat?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [July 22, 2020, 12:17am UTC](https://discuss.elastic.co/t/download-new-version-of-filebeat/241607/4 "2020-07-22T00:17:12Z")

</div>

The default policy is [here](https://github.com/elastic/beats/blob/7a7279fd789d2296dd8c9123bb66b74669d0da51/libbeat/idxmgmt/ilm/config.go#L63-L80);

```
"max_size": "50gb",
"max_age": "30d",

```

You can change the `max_age`n to a day if you want. But that's going to be a bit of a waste to be honest, as your data volumes seem very small.

---

<div class="post-metadata">

**Author:** ![JoseSaborido](https://avatars.discourse-cdn.com/v4/letter/j/9de0a6/32.png) [@JoseSaborido](https://discuss.elastic.co/u/JoseSaborido)\
**Post date:** [July 22, 2020, 11:03am UTC](https://discuss.elastic.co/t/download-new-version-of-filebeat/241607/5 "2020-07-22T11:03:23Z")

</div>

Thanks a lot!

I have added the max age in the Kibana section, is it enough? Or I need to added to the code and build it from source?

We need to put the max\_age in one day because we want to treat the logs daily in order to clean the logs of the day we want and preserve others.

 ![Captura de pantalla 2020-07-22 a las 13.02.31](https://us1.discourse-cdn.com/elastic/original/3X/a/4/a484eaa1580f7bbed0a114f947cd5ca0ef227d61.png)

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [July 22, 2020, 11:16am UTC](https://discuss.elastic.co/t/download-new-version-of-filebeat/241607/6 "2020-07-22T11:16:52Z")

</div>

In Kibana should be sufficient.

---

<div class="post-metadata">

**Author:** ![JoseSaborido](https://avatars.discourse-cdn.com/v4/letter/j/9de0a6/32.png) [@JoseSaborido](https://discuss.elastic.co/u/JoseSaborido)\
**Post date:** [July 23, 2020, 12:58pm UTC](https://discuss.elastic.co/t/download-new-version-of-filebeat/241607/7 "2020-07-23T12:58:53Z")

</div>

Hi I checked today and the index with the new date has not been created

```auto
health status index uuid pri rep docs.count docs.deleted store.size pri.store.size
green open auditbeat-7.4.2-2020.07.01-000001 S_QKJE90R7eo79TZGK2j4A 1 1 92181 0 100.3mb 50.1mb
green open filebeat-7.4.2-2020.07.01-000001 ANqF4ia1RZuqVxDWJgFP2Q 1 1 4254521 0 2.2gb 1.1gb
green open .kibana_task_manager_1 wJO_avJRTp6uhlARdrXlIg 1 1 2 0 64.8kb 32.4kb
green open .apm-agent-configuration C18grt79Qeu1lsMVqDBgqA 1 1 0 0 566b 283b
green open .kibana_1 mlgR3OLGTpKUzFYqWFAWKw 1 1 1350 6 1.2mb 679kb

```

I changed the settings yesterday should I wait more? Or I need others changes?

---

<div class="post-metadata">

**Author:** ![brian\_m](https://avatars.discourse-cdn.com/v4/letter/b/848f3c/32.png) [@brian\_m](https://discuss.elastic.co/u/brian_m)\
**Post date:** [July 23, 2020, 1:19pm UTC](https://discuss.elastic.co/t/download-new-version-of-filebeat/241607/8 "2020-07-23T13:19:56Z")

</div>

I know this seems a silly question, but I've had a few frustrating experiences because I forgot to check, but have you confirmed the correct ILM policy is being applied to the index?

---

<div class="post-metadata">

**Author:** ![JoseSaborido](https://avatars.discourse-cdn.com/v4/letter/j/9de0a6/32.png) [@JoseSaborido](https://discuss.elastic.co/u/JoseSaborido)\
**Post date:** [July 23, 2020, 1:25pm UTC](https://discuss.elastic.co/t/download-new-version-of-filebeat/241607/9 "2020-07-23T13:25:04Z")

</div>

Hi!

Thanks I have the same opinion in this matter but unfortunately after check it uses the the policy we have configured to changed every day:

 ![Captura de pantalla 2020-07-23 a las 15.22.15](https://us1.discourse-cdn.com/elastic/original/3X/6/4/646387796e7bd71f59e39c7068f3f6024cb7f61b.png)  
 ![Captura de pantalla 2020-07-23 a las 15.22.33](https://us1.discourse-cdn.com/elastic/original/3X/c/b/cb05506743049fe98b0ee68be505a6c3979d8283.png)

---

<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:** [August 20, 2020, 3:25pm UTC](https://discuss.elastic.co/t/download-new-version-of-filebeat/241607/10 "2020-08-20T15:25:08Z")

</div>

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