Data ingestion
To begin monitoring your infrastructure and applications, you must pipe data to StackOps Elastic. The amount of resource utilisation charged depends on:
- The amount of data ingested
- The amount of integrations enabled (for Elastic Agents)
- The processors used (for Elastic Agents)
Recommended data ingestion methods
The table below for an overview of the recommended data ingestion methods and its relevant setup guides. To decide which methods to use, refer to Choose data ingestion methods for a more in-depth discussion on the various methods.
| Method | Description | Supported hosts | Relevant setup guides |
|---|---|---|---|
| Rank 1: Recommended | - | - | - |
| Fleet-managed Elastic Agent | Elastic Agent is directly installed onto the host running the software you want to monitor. |
|
|
| Fleet-managed Elastic Agent (for API data collection) |
Elastic Agent installed on a host that acts as an intermediary to fetch or receive data from an external platform via APIs. |
|
|
| Fleet-managed Elastic Agent in containers | Run Elastic Agents in containerised environments. | Containers:
|
|
| Rank 2: Restricted to specific hosts | - | - | - |
| Elastic Serverless Forwarder | Use an AWS Lambda function to ship logs from your AWS environment to Elastic. Recommended if you are monitoring a serverless workload. | AWS Lambda |
| Method | Description | Supported hosts | Relevant setup guides |
|---|---|---|---|
| Elastic APM Agent | Run APM Agents in your application code to measure its performance and track errors. | Code changes at the application level:
|
Related topics
Once data begins streaming into your StackOps Elastic deployment, you should learn more about the following topics:
- Data processing and quality:
- Data storage and lifecycle:
- Security and monitoring:
- Cost management:
