- Elastic Cloud Serverless
- Elasticsearch
- Elastic Observability
- Get started
- Observability overview
- Elastic Observability Serverless billing dimensions
- Create an Observability project
- Quickstart: Monitor hosts with Elastic Agent
- Quickstart: Monitor your Kubernetes cluster with Elastic Agent
- Quickstart: Monitor hosts with OpenTelemetry
- Quickstart: Unified Kubernetes Observability with Elastic Distributions of OpenTelemetry (EDOT)
- Quickstart: Collect data with AWS Firehose
- Get started with dashboards
- Applications and services
- Application performance monitoring (APM)
- Get started with traces and APM
- Learn about data types
- Collect application data
- View and analyze data
- Act on data
- Use APM securely
- Reduce storage
- Managed intake service event API
- Troubleshooting
- Synthetic monitoring
- Get started
- Scripting browser monitors
- Configure lightweight monitors
- Manage monitors
- Work with params and secrets
- Analyze monitor data
- Monitor resources on private networks
- Use the CLI
- Configure a Synthetics project
- Multifactor Authentication for browser monitors
- Configure Synthetics settings
- Grant users access to secured resources
- Manage data retention
- Scale and architect a deployment
- Synthetics Encryption and Security
- Troubleshooting
- Application performance monitoring (APM)
- Infrastructure and hosts
- Logs
- Inventory
- Incident management
- Data set quality
- Observability AI Assistant
- Machine learning
- Reference
- Get started
- Elastic Security
- Elastic Security overview
- Security billing dimensions
- Create a Security project
- Elastic Security requirements
- Elastic Security UI
- AI for Security
- Ingest data
- Configure endpoint protection with Elastic Defend
- Manage Elastic Defend
- Endpoints
- Policies
- Trusted applications
- Event filters
- Host isolation exceptions
- Blocklist
- Optimize Elastic Defend
- Event capture and Elastic Defend
- Endpoint protection rules
- Identify antivirus software on your hosts
- Allowlist Elastic Endpoint in third-party antivirus apps
- Elastic Endpoint self-protection features
- Elastic Endpoint command reference
- Endpoint response actions
- Cloud Security
- Explore your data
- Dashboards
- Detection engine overview
- Rules
- Alerts
- Advanced Entity Analytics
- Investigation tools
- Asset management
- Manage settings
- Troubleshooting
- Manage your project
- Changelog
Get started with system metrics
editGet started with system metrics
editRequired role
The Admin role or higher is required to onboard system metrics data. To learn more, refer to Assign user roles and privileges.
In this guide you’ll learn how to onboard system metrics data from a machine or server, then observe the data in Elastic Observability Serverless.
To onboard system metrics data:
- Create a new Elastic Observability Serverless project, or open an existing one.
- In your Elastic Observability Serverless project, go to Project Settings → Integrations.
- Type System in the search bar, then select the integration to see more details about it.
- Click Add System.
-
Follow the in-product steps to install the System integration and deploy an Elastic Agent. The sequence of steps varies depending on whether you have already installed an integration.
- When configuring the System integration, make sure that Collect metrics from System instances is turned on.
- Expand each configuration section to verify that the settings are correct for your host. For example, you may want to turn on System core metrics to get a complete view of your infrastructure.
Notice that you can also configure the integration to collect logs.
What if Elastic Agent is already running on my host?
Do not try to deploy a second Elastic Agent to the same system. You have a couple options:
- Use the System integration to collect system logs and metrics. To do this, uninstall the standalone agent you deployed previously, then follow the in-product steps to install the System integration and deploy an Elastic Agent.
- Configure your existing standalone agent to collect metrics. To do this, edit the deployed Elastic Agent’s YAML file and add metric inputs to the configuration manually. Manual configuration is a time-consuming process. To save time, you can follow the in-product steps that describe how to deploy a standalone Elastic Agent, and use the generated configuration as source for the input configurations that you need to add to your standalone config file.
After the agent is installed and successfully streaming metrics data, go to Infrastructure → Infrastructure inventory or Hosts to see a metrics-driven view of your infrastructure. To learn more, refer to View infrastructure metrics by resource type or Analyze and compare hosts.
Next steps
editNow that you’ve added metrics and explored your data, learn how to onboard other types of data:
On this page