Data Collection¶
Guance supports collecting performance data and operation status information from hosts, cloud hosts, containers, and other resources to help monitor the infrastructure. The collected data includes core metrics such as CPU, memory, disk, network, etc. After processing, the collected data is displayed through a visualization interface, making it convenient to keep track of the infrastructure's operational status in real time.
Prerequisites
Collection Configuration¶
Host¶
After installing DataKit, the system automatically enables a batch of host-related collectors, which automatically report data to the workspace.
The default enabled collector list is as follows:
Collector Name | Function Description |
---|---|
cpu |
Host CPU usage |
disk |
Disk usage |
diskio |
Host disk IO situation |
mem |
Host memory usage |
swap |
Swap memory usage |
system |
Host operating system load |
net |
Host network traffic situation |
host_process |
List of processes on the host that have been alive for over 10 minutes |
hostobject |
Host basic information (operating system, hardware information, etc.) |
container |
Host container or Kubernetes data (if there are no containers on the host, the collector will exit automatically) |
Note
-
After starting the host collection, modifying the hostname
host_name
will add a new host record while retaining the original hostname; records are removed 24 hours after no data has been reported. -
DataKit counts quantities within 24 hours based on the maximum value, so changing the hostname during the billing cycle will result in being charged for two hosts.
For more details, refer to DataKit Collector Usage, Host Objects.
Cloud Host¶
If DataKit is deployed on a cloud host, you can enable cloud synchronization by setting the cloud_provider
tag. After configuration, simply restart DataKit.
For more details, refer to Enable Cloud Synchronization.
Container¶
Guance provides two ways to enable container data collection:
- Install DataKit on the host: Enable the Container collector to collect Containers and Pods data.
- DaemonSet Installation of DataKit: Supports collecting full container component data (Containers, Pods, Services, etc.).
Process¶
The process collector is enabled by default but does not collect process Metrics data. To collect Metrics data, go to the conf.d/host
folder in the DataKit installation directory, copy host_processes.conf.sample
, rename it to host_processes.conf
, set open_metric
to true
, and then restart DataKit.
For more details, refer to Process.
Resource Catalog¶
By creating custom resources, associating them with the DataKit API and DataFlux Func, any data can be reported to Guance.
For specific operation steps, refer to Resource Catalog Data Reporting.