Architecture

Overview

The KloudMate Agent is installed as a service on the host system, a Docker container, or a DaemonSet on Kubernetes. It is set up during the installation process. The agent is responsible for managing the lifecycle of the Collector. The Agent is not an implementation of the Collector itself — instead, it runs and manages the lifecycle of the existing OTel Collector.

It is also primarily responsible for watching remote configuration (via a REST endpoint) and passing the configuration to the Collector when changes are detected. It has other functionalities such as synthetic monitoring that can be used to monitor the agent's status, and various logs for monitoring purposes.

Each agent is uniquely identifiable, so it can be used to build dashboards for users to monitor the agents and configure them using a web interface.

What the Docker Agent Monitors

Once installed, the Docker Agent collects:

• Container metrics: CPU, memory, network, and disk usage for each running container
• Container lifecycle events: start, stop, restart
• Host metrics: CPU, memory, disk, and network usage of the Docker host
• Container and host logs: stdout/stderr from containers and system logs from host
• Alerts: Configure thresholds for containers or the host to notify on performance issues
• Dashboards: Prebuilt views for container-level and host-level performance This allows you to monitor containers and host together, troubleshoot performance issues, and correlate logs with metrics.

Kubernetes Agent Architecture

The Kubernetes agent runs as a Deployment and DaemonSet and includes:

• Node Monitoring: CPU, memory, disk, and network metrics
• Pod Monitoring: Container-level metrics and logs
• Cluster Events: Kubernetes events and resource monitoring
• Service Discovery: Automatic service endpoint detection

Supported Environments

Future Support

In future releases the agent can also be installed in:

• Mac
• OCI (Oracle Cloud Infrastructure)