Host metrics and logs
Host metrics and logs are what the agent collects automatically, with no setup. As soon as the agent is installed, it starts collecting infrastructure telemetry from the host and sending it to KloudMate. You do not enable anything or write any configuration.
What flows automatically
Section titled “What flows automatically”What the agent collects depends on the deployment mode, because each platform exposes host telemetry differently. Container telemetry is the exception: on any host with a Docker socket, container metrics and logs are collected automatically, whether the agent runs as a Linux service or in Docker mode.
- Host metrics: CPU, memory, disk, network, and process metrics.
- Logs: none are collected from the host automatically. Add application log files with log monitoring, or the systemd journal with a custom config override.
- Docker containers: if the host runs Docker, per-container metrics and logs are collected automatically, the same as in Docker mode. See Monitor Docker containers on the host.
- Host metrics: CPU, memory, disk, and network usage.
- Logs: none are collected from the host automatically, including the Windows Event Log. Add application log files or Event Log channels with log monitoring.
- Application traces: none are collected until you turn on tracing for a service, the same as on Linux. Internet Information Services (IIS) traffic is traced through Event Tracing for Windows (ETW) once you enable it for an application pool. See Windows platform notes.
- Per-node metrics: CPU, memory, disk, and network for each node.
- Pod logs: container stdout and stderr.
- Cluster metrics and events: workload, namespace, and node state, plus cluster events.
- Container metrics: CPU, memory, network, and disk usage for each running container, plus container lifecycle events.
- Container logs: stdout and stderr from each container.
- Host metrics: CPU, memory, disk, and network for the Docker host.
Where to view it
Section titled “Where to view it”Host metrics and logs feed the infrastructure and log views in KloudMate:
- Infrastructure monitoring shows host and container metrics, availability, and trends. See Infrastructure.
- Kubernetes monitoring shows cluster, node, namespace, pod, and workload metrics. See Kubernetes.
- Log Explorer lets you search and filter logs and correlate them with metrics. See Log Explorer.
Collecting custom application logs
Section titled “Collecting custom application logs”The agent does not collect your application log files automatically. To add them, use log monitoring. You point the agent at a folder and file-name pattern, choose how to parse each line, then preview the result before you save. Multiline grouping, for stack traces or pretty-printed JSON, is a modifier you apply on top of any format. For a hand-written receiver in manual mode, see Collect file logs.
What else the agent collects automatically
Section titled “What else the agent collects automatically”Alongside host metrics and logs, two more capabilities turn on without configuration:
- Discovery lists what runs on the host, so you can instrument it. See Discovery.
- eBPF monitoring adds Rate, Errors, and Duration (RED) metrics, a service map, and Database Activity Monitoring, with no code changes. See eBPF observability.