- 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
- Set up Fleet Server
- Install Elastic Agents
- Install Fleet-managed Elastic Agents
- Install standalone Elastic Agents (advanced users)
- Install Elastic Agents in a containerized environment
- Installation layout
- Air-gapped environments
- Use 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
- Manage integrations
- Configure standalone Elastic Agents
- 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
IMPORTANT: No additional bug fixes or documentation updates
will be released for this version. For the latest information, see the
current release documentation.
Create an agent policy without using the UI
editCreate an agent policy without using the UI
editFor use cases where you want to provide a default agent policy or support automation, you can set up an agent policy without using the Fleet UI. To do this, either use the Fleet API or add a preconfigured policy to Kibana:
Option 1. Create an agent policy with the API
editcurl -u <username>:<password> --request POST \ --url <kibana_url>/api/fleet/agent_policies?sys_monitoring=true \ --header 'content-type: application/json' \ --header 'kbn-xsrf: true' \ --data '{"name":"Agent policy 1","namespace":"default","monitoring_enabled":["logs","metrics"]}'
In this API call:
-
sys_monitoring=true
adds the system integration to the agent policy -
monitoring_enabled
turns on Elastic Agent monitoring
For more information, refer to Kibana Fleet APIs.
Option 2. Create agent policies with preconfiguration
editAdd preconfigured policies to kibana.yml
config.
For example, the following example adds a Fleet Server policy for self-managed setup:
xpack.fleet.packages: - name: fleet_server version: latest xpack.fleet.agentPolicies: - name: Fleet Server policy id: fleet-server-policy namespace: default package_policies: - name: fleet_server-1 package: name: fleet_server
The following example creates an agent policy for general use:
xpack.fleet.packages: - name: system version: latest - name: elastic_agent version: latest xpack.fleet.agentPolicies: - name: Agent policy 1 id: agent-policy-1 namespace: default monitoring_enabled: - logs - metrics package_policies: - name: system-1 id: default-system package: name: system
For more information about preconfiguration settings, refer to the Kibana documentation.
On this page
Was this helpful?
Thank you for your feedback.