LogicMonitor's Kubernetes Monitoring Overview

Last updated on 01 June, 2023

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. In addition, LogicMonitor officially supports running LM Container Kubernetes Monitoring on AWS Bottlerocket OS: https://aws.amazon.com/bottlerocket/.

LogicMonitor’s Kubernetes version support policy aligns with the policies of major cloud providers’ Kubernetes services: EKS (AWS)AKS (Azure)GKE (GCP), and OpenShift (RedHat). We additionally adhere to the Kubernetes community’s support for different Kubernetes versions. This results in us offering support for all the Kubernetes versions that are backed by these four cloud services and the community. The following current calendar for LM Container support for upstream Kubernetes releases is updated regularly to reflect the ongoing support from these providers and the Kubernetes community.

Kubernetes VersionUpstream Release DateLM Container End of Support
1.27
(Recommended)
11 April 2023June 2024
1.266 December 2022June 2024
1.2523 August 2022May 2024
1.243 May 2022January 2024
1.2314 December 2021October 2023

The following table displays the supported OpenShift versions:

OpenShift VersionGeneral AvailabilityLM Container End of Support
4.12
(Recommended)
17 January 202317 March 2024
4.1110 August 202210 October 2023
4.1010 March 202210 July 2023

The following table displays the supported Kubernetes and Helm versions with the compatible LM Container Chart, Argus, and Collectorset-Controller versions.

LM Container Chart

Kubernetes VersionHelm VersionLM Container Chart
1.27
(Recommended)
33.5.0 or later
1.2633.5.0 or later
1.2533.5.0 or later
1.2431.0.0 or later
1.2331.0.0 or later

Argus and Collectorset-Controller

Kubernetes VersionHelm
Version
Argus
Version
Collectorset-Controller Version
1.27
(Recommended)
3v7v3
1.263v7v3
1.253v6, v7v2, v3
1.243v6, v7v2, v3
1.233v6, v7v2, v3

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 earlier table, versions are referenced according to the major version number, to view all the available image tags, see DockerHub.

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 to 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.

Supported Resources

The following resources are supported for monitoring:

LM Container Chart

Argus

Performance Optimization and Tuning Recommendations

The following table provides guidelines on provisioning resources for LogicMonitor components to have optimum performance and reliable monitoring for the Kubernetes cluster:

Collector SizeMediumLarge 
Maximum Resources with 1 collector replica1300 resources3600 resources
Argus and CSC VersionArgus Version – v7.1.2
CSC Version – v3.1.2
Argus Version – v7.1.2
CSC Version – v3.1.2
Collector VersionGD 33.001 GD 33.002 
Recommended Argus limits & RequestsCPU Requests – 0.256 core
CPU Limits – 0.5 core
CPU Requests – 0.5 core
CPU Limits – 1 core
Memory Requests – 250MB
Memory Limits – 500MB
Memory Requests – 500MB
Memory Limits – 1GB

Recommended Collectorset Controller limits & Requests
CPU Requests – 0.02 core
CPU Limits – 0.05 core
CPU Requests – 0.02 core CPU Limits – 0.05 core
Memory Requests – 150MB
Memory Limits – 200MB
Memory Requests – 150MB
Memory Limits – 200MB

Getting Started

To get started, you can navigate to the Resources page > Add > Kubernetes Cluster to add Kubernetes clusters. For more information, see Adding Your Kubernetes Cluster into Monitoring.

In This Article