LogicMonitor's Kubernetes Monitoring Overview
Last updated on 01 June, 2023LogicMonitor’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 Version | Upstream Release Date | LM Container End of Support |
| 1.27 (Recommended) | 11 April 2023 | June 2024 |
| 1.26 | 6 December 2022 | June 2024 |
| 1.25 | 23 August 2022 | May 2024 |
| 1.24 | 3 May 2022 | January 2024 |
| 1.23 | 14 December 2021 | October 2023 |
The following table displays the supported OpenShift versions:
| OpenShift Version | General Availability | LM Container End of Support |
| 4.12 (Recommended) | 17 January 2023 | 17 March 2024 |
| 4.11 | 10 August 2022 | 10 October 2023 |
| 4.10 | 10 March 2022 | 10 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 Version | Helm Version | LM Container Chart |
| 1.27 (Recommended) | 3 | 3.5.0 or later |
| 1.26 | 3 | 3.5.0 or later |
| 1.25 | 3 | 3.5.0 or later |
| 1.24 | 3 | 1.0.0 or later |
| 1.23 | 3 | 1.0.0 or later |
Argus and Collectorset-Controller
| Kubernetes Version | Helm Version | Argus Version | Collectorset-Controller Version |
| 1.27 (Recommended) | 3 | v7 | v3 |
| 1.26 | 3 | v7 | v3 |
| 1.25 | 3 | v6, v7 | v2, v3 |
| 1.24 | 3 | v6, v7 | v2, v3 |
| 1.23 | 3 | v6, v7 | v2, 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 Size | Medium | Large |
| Maximum Resources with 1 collector replica | 1300 resources | 3600 resources |
| Argus and CSC Version | Argus Version – v7.1.2 CSC Version – v3.1.2 | Argus Version – v7.1.2 CSC Version – v3.1.2 |
| Collector Version | GD 33.001 | GD 33.002 |
| Recommended Argus limits & Requests | CPU 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.