# Filebeat 8.3

**URL:** <https://discuss.elastic.co/t/filebeat-8-3/314630>\
**Category:** Beats\
**Tags:** filebeat, metricbeat\
**Created:** [September 17, 2022, 11:52pm UTC](https://discuss.elastic.co/t/filebeat-8-3/314630 "2022-09-17T23:52:30Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [September 19, 2022, 12:54am UTC](https://discuss.elastic.co/t/filebeat-8-3/314630/8 "2022-09-19T00:54:03Z")

</div>

@abaltan

Does the above help or do you have a more specific question.

> `auto` is no longer a valid setting it was a valid setting in 7.x ... in the Past 7.x `auto` was (the default) is specified on version 7.0 and later, Filebeat automatically uses index lifecycle management if the feature is enabled in Elasticsearch and has the required license; \> otherwise, Filebeat creates daily indices.
> 
> `true` and `false` is much cleaner now  
> Either `true` you use the setting in the filebeat.yml or `false` you do not.

ILM is a big topic.. basically the way you are doing it is daily indices (rollover)... if you want to use hot / warm etc you will need to setup and ILM policy and map it into the index template .. .by default it will use the filebeat ILM policy... below I showed you how to name your own policy which you would create.

I noticed a few other things in your config above.  
You had an extra `setup.ilm.enabled: false` at the top

Also I cleaned up the names and the template name etc.. etc.. I think this will work better for you

You need to run `filebeat setup -e` to load / create the template at least once.

Here is my cleaned up version with some side notes for you. This is 8.x so it filebeat uses data streams by default perhaps take a glance at that!

```auto
filebeat.inputs:
- type: log
  enabled: true
  paths:
   - /Users/sbrown/workspace/sample-data/discuss/container-mixed/*.log
  # json.keys_under_root: true
  # json.add_error_key: true
  # json.message_key: log

filebeat.config.modules:
  path: ${path.config}/modules.d/*.yml
  reload.enabled: false

setup.template.settings:
  index.number_of_shards: 1
  index.number_of_replicas: 0
  index.codec: best_compression

name: "apigee-dev-beat"
tags: ["apigee-dev-beat"]

setup.ilm.enabled: true
setup.ilm.rollover_alias: "api-log"
setup.ilm.pattern: "{now/d}-000001"

output.elasticsearch:
  hosts: ["localhost:9200"]
  index: "api-log-%{[agent.version]}" <!---- Don't add -%{+yyyy.MM.dd} its a data strean and getts added to the backing index automatically
  # ssl.verification_mode: none
  # username: [username]
  # password: [passwrod]
  # pipeline: "geoip"

setup.template.enabled: true <!--- You should explicitly set this 
setup.template.name: "api-log-%{[agent.version]}" <!----This needs to match the index name because now it is a data stream
setup.template.pattern: "api-log-%{[agent.version]}" <!-- Better matching Hygiene because it is a data stream 
setup.template.overwrite: false <!--- Careful with this if set to true it will overwrite every time.
setup.ilm.policy_name: api-policy <!---- If you want to use your own policy 
setup.template.append_fields:
  - name: apitimestamp
    type: date
# # format: "strict_date_optional_time||epoch_millis||yyyy-MM-dd'T'HH:mm:ss.SSS||yyyy-MM-dd'T'HH:mm:ssZZ"

processors:
  - add_host_metadata: ~
  - add_cloud_metadata: ~

```

Results template

 ![Screen Shot 2022-09-18 at 6.35.13 PM](https://us1.discourse-cdn.com/elastic/original/3X/9/e/9edd5fca909f223d06fc3f830ee2c0e602f21998.png)

Data Stream

 ![Screen Shot 2022-09-18 at 5.57.18 PM](https://us1.discourse-cdn.com/elastic/original/3X/7/8/78cb81cd81a5fef6aebe935c43e8f9e0ad074941.png)

Backing index

 ![Screen Shot 2022-09-18 at 5.57.57 PM](https://us1.discourse-cdn.com/elastic/original/3X/b/b/bbb60442b8cfd222236478977fad1b4b9074b2b8.png)

---

_[View the full topic](https://discuss.elastic.co/t/filebeat-8-3/314630)._