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 the 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 hosts together, troubleshoot performance issues, and correlate logs with metrics the docker agent requires docker sock to be mounted to the agent container 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