Support > Monitoring > Containers > Kubernetes > About Logicmonitors Kubernetes Monitoring

About LogicMonitor’s Kubernetes Monitoring

Overview

LogicMonitor’s Kubernetes Monitoring Integration enables comprehensive monitoring for Kubernetes Clusters and the containerized applications running within.

Compatibility

LogicMonitor officially supports the most recent four versions of Kubernetes at any given time, and aims to offer support for new versions within 60 days of the official release. Additionally, LogicMonitor officially supports running LM Container Kubernetes Monitoring on AWS Bottlerocket OS: https://aws.amazon.com/bottlerocket/.

The following table displays supported Kubernetes and Helm version with the compatible Argus and Collectorset-Controller versions.

Kubernetes
Version		Helm
Version		Argus
Version 		Collectorset-Controller Version
1.152v2, latestv1, latest
1.163v3, v4v2
1.173v3, v4v2
1.183v3, v4v2

Note: Referencing the image tag by its major version number (such as v3) also matches the versions with incremented minor and bug fix version numbers while also allowing you to specify an exact version. In the table above versions are referenced according the major version number, but you should refer to DockerHub for all available image tags.

Dependencies

The integration relies on two lightweight applications that each run in your cluster as a pod:

  • An application, Argus, running in the cluster for discovery. Argus uses LogicMonitor’s API to add Nodes, Pods, and Services into monitoring.
  • A Collectorset-Controller that manages one or more Dockerized LogicMonitor Collectors for data collection. Once Kubernetes Cluster resources are added into LogicMonitor, data collection starts automatically. Data is collected for Nodes, Pods, Containers, and Services via the Kubernetes API. Additionally, standard containerized applications (e.g. Redis, MySQL, etc.) will be automatically detected and monitored.

Note: LogicMonitor’s Kubernetes monitoring integration is an add-on feature called LM Container. You may need to reach out to your Customer Success Manager (CSM) to get started.

Getting Started

To get started, you have two options:

In this Article: