This functionality is in beta and is subject to change. The design and code is less mature than official GA features and is being provided as-is with no warranties. Beta features are not subject to the support SLA of official GA features.
We have collected the most frequently asked questions here. If your question isn’t answered here, contact us in the discuss forum. Your feedback is very valuable to us.
Also read Troubleshoot common problems.
Why doesn’t my enrolled agent show up in the Fleet app?edit
If Elastic Agent was successfully enrolled, but doesn’t show up in the Agents list,
it might not be started. Make sure the
elastic-agent process is running on
the host. If it’s not running, use the
command to start it. The most common way to deploy an Elastic Agent is by using
install command. This command starts the Elastic Agent for you.
Where does Elastic Agent store logs after startup?edit
When started successfully, Metricbeat logs are stored in
data/logs/metricbeat under the folder where Elastic Agent was started. If that log
path does not exist, Elastic Agent was unable to start Metricbeat, which is a
higher level problem to triage. Usually you can see these logs in the Fleet
UI, unless there are problems severe enough that the Elastic Agent or its related
processes cannot send data to Elasticsearch.
What policy is the Elastic Agent running?edit
To find the policy file, inspect the
elastic-agent.yml file in the
directory where Elastic Agent is running. Not sure where the agent is running? See
If the agent is running in Fleet mode, this file contains the following citation:
fleet: enabled: true
action_store.yml file (located under
data/elastic-agent-*) contains the
entire, unencrypted policy.
To see the Elasticsearch location, look at the
outputs. For example:
outputs: default: api_key: Aq-mPpcBDA7TmnriKCSD:Np6NAleNQ1mMpgN_JPYazw hosts: - https://3m63533c175a4036b3d8bbe7bd462fa3.us-east-1.aws.found.io:443 type: elasticsearch
This file also shows the version of all packages used by the current policy.
To see the Elastic Agent version, run:
Why can’t I see the data Elastic Agent is sending?edit
If Elastic Agent is set up and running, but you don’t see data in Kibana:
Go to Management > Dev Tools in Kibana, and in the Console, search your index for data. For example:
Or if you prefer, go to the Discover app.
Look at the data that Elastic Agent has sent and see if the
name.hostfield contains your host machine name.
If you don’t see data for your host, it’s possible that the data is blocked in the network, or that a firewall or security problem is preventing the Elastic Agent from sending the data.
Although it’s redundant to install stand-alone Metricbeat, you might want to try installing it to see if it’s able to send data successfully to Elasticsearch. For more information, see Metricbeat quick start.
If Metricbeat is able to send data to Elasticsearch, there is possibly a bug or problem with Elastic Agent, and you should report it.
How do I restore an Elastic Agent that I deleted from Fleet?edit
It’s ok, we’ve got your back! The data is still in Elasticsearch. To add Elastic Agent to Fleet again, Stop Elastic Agent, re-enroll it on the host, then run Elastic Agent.
How do I restart Elastic Agent after rebooting my host?edit
Elastic Agent should restart automatically when you reboot your host. If it doesn’t, you can start it manually by running:
If the process is already running, you can restart it by running:
Does Elastic Agent or Kibana download integration packages?edit
Elastic Agent does not download integration packages. When you add an integration in
Fleet, Kibana connects to the Elastic Package Registry at
downloads the integration package, and stores its assets in Elasticsearch. This means
that you no longer have to run a manual setup command to load integrations as
you did previously with Beats modules.
Does Elastic Agent download anything from the Internet?edit
As of 7.10 and beyond, the endpoint security capabilities are bundled with Elastic Agent, so a fully capable artifact can be installed with no connection to the Elastic download site. However, if it is in use, the Endpoint Security process is instructed to attempt to download newer released versions of the integration specific artifacts it uses. Some of those are, for example, the malware model, trusted apps artifact, exceptions list artifact, and others. For more information, see the Elastic Security solution documentation.
Do I need to set up the Beats managed by Elastic Agent?edit
You might have noticed that Elastic Agent runs Beats under the hood. But note that the Beats managed by Elastic Agent are set up and run differently from standalone Beats.
For example, standalone Beats use modules and require you to run a setup
command on the host to load assets, such as ingest pipelines and dashboards. In
contrast, Beats managed by Elastic Agent use integration packages that Kibana
downloads from the Elastic Package Registry at
epr.elastic.co. This means that
Elastic Agent does not need extra privileges to set up assets because
Fleet manages the assets.
What is the Endpoint Security integration in Fleet?edit
The Endpoint Security integration provides protection on your Elastic Agent controlled host. The integration monitors your host for security-related events, allowing for investigation of security data through the Elastic Security app in Kibana. The Endpoint Security integration is managed by Elastic Agent in the same way as other integrations. Try it out! For more information, see the Elastic Security documentation.
How are communications secured between Elastic Security and Elastic Agent?edit
Elastic Security connects to the agent over loopback TLS on port 6788. Elastic Security validates that the agent has root (Linux and macOS) or SYSTEM (Windows) permissions.
How are communications secured between Elastic Agent and Kibana?edit
Elastic Agent connects to Kibana over TLS and authenticates the certificate presented by Kibana. The agent then provides an API key as an authentication token, which Kibana validates.
Which Elasticsearch and Kibana ports need to be accessible?edit
The policy generated by Fleet already contains the correct Elasticsearch address
and port for your setup. If you run everything locally, the address is
127.0.0.1:9200. If you use our
hosted Elasticsearch Service on Elastic Cloud,
you can copy the Elasticsearch endpoint URL from the overview page of your deployment.
If you’re not running in Elastic Cloud, make sure the Kibana and Elasticsearch HTTPS ports
are both accessible; by default these are