Load the Elasticsearch index template [auditbeat-template]

{{es}} uses index templates to define:

Settings that control the behavior of your data stream and backing indices. The settings include the lifecycle policy used to manage backing indices as they grow and age.
Mappings that determine how fields are analyzed. Each mapping sets the {{es}} datatype to use for a specific data field.

The recommended index template file for Auditbeat is installed by the Auditbeat packages. If you accept the default configuration in the auditbeat.yml config file, Auditbeat loads the template automatically after successfully connecting to {{es}}. If the template already exists, it’s not overwritten unless you configure Auditbeat to do so.

::::{note} A connection to {{es}} is required to load the index template. If the output is not {{es}} (or {{ech}}), you must load the template manually. ::::

This page shows how to change the default template loading behavior to:

Load your own index template
Overwrite an existing index template
Disable automatic index template loading
Load the index template manually

For a full list of template setup options, see Elasticsearch index template.

Load your own index template [load-custom-template]

To load your own index template, set the following options:

yaml

setup.template.name: "your_template_name"
setup.template.fields: "path/to/fields.yml"

If the template already exists, it’s not overwritten unless you configure Auditbeat to do so.

You can load templates for both data streams and indices.

Overwrite an existing index template [overwrite-template]

::::{warning} Do not enable this option for more than one instance of Auditbeat. If you start multiple instances at the same time, it can overload your {{es}} with too many template update requests. ::::

To overwrite a template that’s already loaded into {{es}}, set:

yaml

setup.template.overwrite: true

Disable automatic index template loading [disable-template-loading]

You may want to disable automatic template loading if you’re using an output other than {{es}} and need to load the template manually. To disable automatic template loading, set:

yaml

setup.template.enabled: false

If you disable automatic template loading, you must load the index template manually.

Load the index template manually [load-template-manually]

To load the index template manually, run the setup command. A connection to {{es}} is required. If another output is enabled, you need to temporarily disable that output and enable {{es}} by using the -E option. The examples here assume that Logstash output is enabled. You can omit the -E flags if {{es}} output is already enabled.

If you are connecting to a secured {{es}} cluster, make sure you’ve configured credentials as described in the Quick start: installation and configuration.

If the host running Auditbeat does not have direct connectivity to {{es}}, see Load the index template manually (alternate method).

To load the template, use the appropriate command for your system.

deb and rpm:

auditbeat setup --index-management -E output.logstash.enabled=false -E 'output.elasticsearch.hosts=["localhost:9200"]'

mac:

./auditbeat setup --index-management -E output.logstash.enabled=false -E 'output.elasticsearch.hosts=["localhost:9200"]'

linux:

./auditbeat setup --index-management -E output.logstash.enabled=false -E 'output.elasticsearch.hosts=["localhost:9200"]'

docker:

docker run --rm docker.elastic.co/beats/auditbeat:{{version.stack}} setup --index-management -E output.logstash.enabled=false -E 'output.elasticsearch.hosts=["localhost:9200"]'

win:

Open a PowerShell prompt as an Administrator (right-click the PowerShell icon and select Run As Administrator).

From the PowerShell prompt, change to the directory where you installed Auditbeat, and run:

PS > .\auditbeat.exe setup --index-management -E output.logstash.enabled=false -E 'output.elasticsearch.hosts=["localhost:9200"]'

Load the index template manually (alternate method) [load-template-manually-alternate]

If the host running Auditbeat does not have direct connectivity to {{es}}, you can export the index template to a file, move it to a machine that does have connectivity, and then install the template manually.

To export the index template, run:

deb and rpm:

auditbeat export template > auditbeat.template.json

mac:

./auditbeat export template > auditbeat.template.json

linux:

./auditbeat export template > auditbeat.template.json

win:

PS > .\auditbeat.exe export template --es.version {{version.stack}} | Out-File -Encoding UTF8 auditbeat.template.json

To install the template, run:

deb and rpm:

curl -XPUT -H 'Content-Type: application/json' http://localhost:9200/_index_template/auditbeat-{{version.stack}} [email protected]

mac:

curl -XPUT -H 'Content-Type: application/json' http://localhost:9200/_index_template/auditbeat-{{version.stack}} [email protected]

linux:

curl -XPUT -H 'Content-Type: application/json' http://localhost:9200/_index_template/auditbeat-{{version.stack}} [email protected]

win:

PS > Invoke-RestMethod -Method Put -ContentType "application/json" -InFile auditbeat.template.json -Uri http://localhost:9200/_index_template/auditbeat-{{version.stack}}

Once you have loaded the index template, load the data stream as well. If you do not load it, you have to give the publisher user manage permission on auditbeat-{{version.stack}} index.

deb and rpm:

curl -XPUT http://localhost:9200/_data_stream/auditbeat-{{version.stack}}

mac:

curl -XPUT http://localhost:9200/_data_stream/auditbeat-{{version.stack}}

linux:

curl -XPUT http://localhost:9200/_data_stream/auditbeat-{{version.stack}}

win:

PS > Invoke-RestMethod -Method Put -Uri http://localhost:9200/_data_stream/auditbeat-{{version.stack}}