Monitor hosts with Elastic Agent
editMonitor hosts with Elastic Agent
edit[preview] This functionality is in technical preview and may be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features.
In this quickstart guide, you’ll learn how to scan your host to detect and collect logs and metrics, then navigate to dashboards to further analyze and explore your observability data. You’ll also learn how to get value out of your observability data.
To scan your host, you’ll run an auto-detection script that downloads and installs Elastic Agent, which is used to collect observability data from the host and send it to Elastic.
The script also generates an Elastic Agent configuration file that you can use with your existing Infrastructure-as-Code tooling.
Prerequisites
edit- An Observability project. To learn more, refer to Create an Observability project.
- A user with the Admin role or higher—required to onboard system logs and metrics. To learn more, refer to Assign user roles and privileges.
- Root privileges on the host—required to run the auto-detection script used in this quickstart.
Limitations
edit- The auto-detection script currently scans for metrics and logs from Apache, Docker, Nginx, and the host system. It also scans for custom log files.
-
The auto-detection script works on Linux and MacOS only. Support for the
lsof
command is also required if you want to detect custom log files. - If you’ve installed Apache or Nginx in a non-standard location, you’ll need to specify log file paths manually when you run the scan.
- Because Docker Desktop runs in a VM, its logs are not auto-detected.
Collect your data
edit- Create a new Observability project, or open an existing one.
- In your Observability project, go to Add Data.
- Select Collect and analyze logs, and then select Auto-detect logs and metrics.
-
Copy the command that’s shown. For example:
You’ll run this command to download the auto-detection script and scan your system for observability data.
- Open a terminal on the host you want to scan, and run the command.
-
Review the list of log files:
-
Enter
Y
to ingest all the log files listed. -
Enter
n
to either exclude log files or specify additional log paths. EnterY
to confirm your selections.
-
Enter
When the script is done, you’ll see a message like "Elastic Agent is configured and running."
There might be a slight delay before logs and other data are ingested.
Need to scan your host again?
You can re-run the script on the same host to detect additional logs.
The script will scan the host and reconfigure Elastic Agent with any additional logs that are found.
If the script misses any custom logs, you can add them manually by entering n
after the script has finished scanning the host.
Visualize your data
editAfter installation is complete and all relevant data is flowing into Elastic, the Visualize your data section will show links to assets you can use to analyze your data. Depending on what type of observability data was collected, the page may link to the following integration assets:
Integration asset | Description |
---|---|
System |
Prebuilt dashboard for monitoring host status and health using system metrics. |
Apache |
Prebuilt dashboard for monitoring Apache HTTP server health using error and access log data. |
Docker |
Prebuilt dashboard for monitoring the status and health of Docker containers. |
Nginx |
Prebuilt dashboard for monitoring Nginx server health using error and access log data. |
Custom .log files |
Logs Explorer for analyzing custom logs. |
For example, you can navigate the Host overview dashboard to explore detailed metrics about system usage and throughput. Metrics that indicate a possible problem are highlighted in red.
Get value out of your data
editAfter using the dashboards to examine your data and confirm you’ve ingested all the host logs and metrics you want to monitor, you can use Observability to gain deeper insight into your data.
For host monitoring, the following capabilities and features are recommended:
-
In the Infrastructure UI, analyze and compare data collected from your hosts. You can also:
- Detect anomalies for memory usage and network traffic on hosts.
- Create alerts that notify you when an anomaly is detected or a metric exceeds a given value.
-
In the Logs Explorer, search and filter your log data, get information about the structure of log fields, and display your findings in a visualization. You can also:
- Monitor log data set quality to find degraded documents.
- Run a pattern analysis to find patterns in unstructured log messages.
- Create alerts that notify you when an Observability data type reaches or exceeds a given value.
-
Use AIOps features to apply predictive analytics and machine learning to your data:
- Detect anomalies by comparing real-time and historical data from different sources to look for unusual, problematic patterns.
- Analyze log spikes and drops.
- Detect change points in your time series data.
Refer to Observability overview for a description of other useful features.