- Fleet and Elastic Agent Guide: other versions:
- Fleet and Elastic Agent overview
- Beats and Elastic Agent capabilities
- Quick starts
- Migrate from Beats to Elastic Agent
- Deployment models
- Install Elastic Agents
- Install Fleet-managed Elastic Agents
- Install standalone Elastic Agents
- Install Elastic Agents in a containerized environment
- Run Elastic Agent in a container
- Run Elastic Agent on Kubernetes managed by Fleet
- Advanced Elastic Agent configuration managed by Fleet
- Configuring Kubernetes metadata enrichment on Elastic Agent
- Run Elastic Agent on GKE managed by Fleet
- Run Elastic Agent on Amazon EKS managed by Fleet
- Run Elastic Agent on Azure AKS managed by Fleet
- Run Elastic Agent Standalone on Kubernetes
- Scaling Elastic Agent on Kubernetes
- Using a custom ingest pipeline with the Kubernetes Integration
- Environment variables
- Installation layout
- Air-gapped environments
- Using a proxy server with Elastic Agent and Fleet
- Uninstall Elastic Agents from edge hosts
- Start and stop Elastic Agents on edge hosts
- Elastic Agent configuration encryption
- Secure connections
- Manage Elastic Agents in Fleet
- Configure standalone Elastic Agents
- Create a standalone Elastic Agent policy
- Structure of a config file
- Inputs
- Providers
- Outputs
- SSL/TLS
- Logging
- Feature flags
- Agent download
- Config file examples
- Grant standalone Elastic Agents access to Elasticsearch
- Example: Use standalone Elastic Agent with Elastic Cloud Serverless to monitor nginx
- Example: Use standalone Elastic Agent with Elasticsearch Service to monitor nginx
- Debug standalone Elastic Agents
- Kubernetes autodiscovery with Elastic Agent
- Monitoring
- Reference YAML
- Manage integrations
- Define processors
- Processor syntax
- add_cloud_metadata
- add_cloudfoundry_metadata
- add_docker_metadata
- add_fields
- add_host_metadata
- add_id
- add_kubernetes_metadata
- add_labels
- add_locale
- add_network_direction
- add_nomad_metadata
- add_observer_metadata
- add_process_metadata
- add_tags
- community_id
- convert
- copy_fields
- decode_base64_field
- decode_cef
- decode_csv_fields
- decode_duration
- decode_json_fields
- decode_xml
- decode_xml_wineventlog
- decompress_gzip_field
- detect_mime_type
- dissect
- dns
- drop_event
- drop_fields
- extract_array
- fingerprint
- include_fields
- move_fields
- parse_aws_vpc_flow_log
- rate_limit
- registered_domain
- rename
- replace
- script
- syslog
- timestamp
- translate_sid
- truncate_fields
- urldecode
- Command reference
- Troubleshoot
- Release notes
Enabling and disabling advanced indexing features for Fleet-managed data streams
editEnabling and disabling advanced indexing features for Fleet-managed data streams
editFleet provides support for several advanced features around its data streams, including:
These features can be enabled and disabled for Fleet-managed data streams by using the index template API and a few key settings.
If you are already making use of @custom
component templates for ingest or retention customization (as shown for example in Tutorial: Customize data retention policies), exercise care to ensure you don’t overwrite your customizations when making these requests.
We recommended using Kibana Dev Tools to run the following requests. Replace <NAME>
with the name of a given integration data stream. For example specifying metrics-nginx.stubstatus
results in making a PUT request to _component_template/metrics-nginx.stubstatus@custom
. Use the index management interface to explore what integration data streams are available to you.
Once you’ve executed a given request below, you also need to execute a data stream rollover to ensure any incoming data is ingested with your new settings immediately. For example:
POST metrics-nginx.stubstatus-default/_rollover
Refer to the following steps to enable or disable advanced data stream features:
Enable TSDS
editTSDS uses synthetic _source
, so if you want to trial both features you need to enable only TSDS.
Due to restrictions in the Elasticsearch API, TSDS must be enabled at the index template level. So, you’ll need to make some sequential requests to enable or disable TSDS.
-
Send a GET request to retrieve the index template:
GET _index_template/<NAME>
-
Use the JSON payload returned from the GET request to populate a PUT request, for example:
PUT _index_template/<NAME> { # You can copy & paste this directly from the GET request above "index_patterns": [ "<index pattern from GET request>" ], # Make sure this is added "template": { "settings": { "index": { "mode": "time_series" } } }, # You can copy & paste this directly from the GET request above "composed_of": [ "<NAME>@package", "<NAME>@custom", ".fleet_globals-1", ".fleet_agent_id_verification-1" ], # You can copy & paste this directly from the GET request above "priority": 200, # Make sure this is added "data_stream": { "allow_custom_routing": false } }
Disable TSDS
editTo disable TSDS, follow the same procedure as to enable TSDS, but specify null
for index.mode
instead of time_series
. Follow the steps below or you can copy the NGINX example.
-
Send a GET request to retrieve the index template:
GET _index_template/<NAME>
-
Use the JSON payload returned from the GET request to populate a PUT request, for example:
PUT _index_template/<NAME> { # You can copy/paste this directly from the GET request above "index_patterns": [ "<index pattern from GET request>" ], # Make sure this is added "template": { "settings": { "index": { "mode": null } } }, # You can copy/paste this directly from the GET request above "composed_of": [ "<NAME>@package", "<NAME>@custom", ".fleet_globals-1", ".fleet_agent_id_verification-1" ], # You can copy/paste this directly from the GET request above "priority": 200, # Make sure this is added "data_stream": { "allow_custom_routing": false } }
For example, the following payload disables TSDS on
nginx.stubstatus
:{ "index_patterns": [ "metrics-nginx.stubstatus-*" ], "template": { "settings": { "index": { "mode": null } } }, "composed_of": [ "metrics-nginx.stubstatus@package", "metrics-nginx.stubstatus@custom", ".fleet_globals-1", ".fleet_agent_id_verification-1" ], "priority": 200, "data_stream": { "allow_custom_routing": false } }
Enable synthetic _source
editPUT _component_template/<NAME>@custom { "template": { "mappings": { "_source": { "mode": "synthetic" } } } }
Disable synthetic _source
editPUT _component_template/<NAME>@custom { "template": { "mappings": { "_source": {} } } }