- 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 (advanced users)
- Install Elastic Agents in a containerized environment
- Run Elastic Agent in a container
- Run Elastic Agent on Kubernetes managed by Fleet
- 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 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
Install and uninstall Elastic Agent integration assets
editInstall and uninstall Elastic Agent integration assets
editElastic Agent integrations come with a number of assets, such as dashboards, saved searches, and visualizations for analyzing data. When you add an integration to an agent policy in Fleet, the assets are installed automatically. If you’re building a policy file by hand, you need to install required assets such as index templates.
Install integration assets
edit- In Kibana, go to Management > Integrations > Browse integrations. Search for and select an integration. You can select a category to narrow your search.
- Click the Settings tab.
- Click Install <integration> assets to set up the Kibana and Elasticsearch assets.
There are a couple of things to note about installing integration assets:
- Elastic Agent integration assets can be installed only on a single Kibana space. If you want to access assets in a different space, you can copy them.
- It’s currently not possible to have multiple versions of the same integration installed. When you upgrade an integration, the previous version assets are removed and replaced by the current version.
Uninstall integration assets
editUninstall an integration to remove all Kibana and Elasticsearch assets that were installed by the integration.
-
Before uninstalling an integration, delete the integration policy from any Elastic Agent policies that use it.
Any Elastic Agents enrolled in the policy will stop using the deleted integration.
- In Kibana, go to Management > Integrations > Installed integrations. Search for and select an integration.
- Click the Settings tab.
- Click Uninstall <integration> to remove all Kibana and Elasticsearch assets that were installed by this integration.
Reinstall integration assets
editYou may need to reinstall an integration package to resolve a specific problem, such as:
- An asset was edited manually, and you want to reset assets to their original state.
- A temporary problem (like a network issue) occurred during package installation or upgrade.
- A package was installed in a prior version that had a bug in the install code.
To reinstall integration assets:
- In Kibana, go to Management > Integrations > Installed integrations. Search for and select an integration.
- Click the Settings tab.
- Click Reinstall <integration> to set up the Kibana and Elasticsearch assets.