Come join our live training webinar every other Wednesday at 11am PST and hear LogicMonitor experts explain best practices and answer common questions. We understand these are uncertain times, and we are here to help!
This topic discusses how to add a Kubernetes cluster to your monitored resources.
1. Import the most recent suite of Kubernetes DataSources from LogicMonitor’s Repository: Settings > DataSources > Add > From LogicMonitor’s Repository
2. On the Resource page, select Add > Kubernetes Cluster. In case you are unable to see the Kubernetes Cluster option, contact your Customer Success Manager (CSM).
3. In the Add Kubernetes Cluster setup wizard, complete the three steps: (1) General Information, (2) Install Argus, and (3) Add Services.
Fill in the following general information:
4. In the Collector Information section, enter the number of Collector replicas (Required), a Collector size, and a Collector escalation chain. These fields control how many containerized Collectors run with the cluster, what size those Collectors are, and where “Collector down” alerts get routed.
You require the following permissions to install clusters:
To exclude the resources from monitoring, complete the following steps:
1. On the Resource page, select Add > Kubernetes Cluster.
2. On the Add Kubernetes Cluster setup wizard, in the General Information section, enable the Exclude resources from discovery option.
3. Add Labels key and Label Values for the required resources and click Save.
4. Add the required information in the General Information, Install Argus, and Add Services section.
As shown in the earlier image, all the deployments with Label Key as “app” and Label Value as “QA” or “DEV” and all the pods with name as “test1” will be excluded from monitoring.
Note: If you using Argus v6.0 or later, and the existing filtering configuration contains “ * ” for excluding all the resources from monitoring, you must remove “ * ” from the filtering configuration.
For information on upgrading to Argus v6, see How to Upgrade to Argus v6.
If you are using v5 or previous, you can exclude all the resources by adding * in LabelKey and LabelValue. However, this feature is available only for Argus versions earlier than v6. For example:
With the following command, you can exclude all the services and deployments from monitoring:--set filters.service=\"*\" --set filters.deployment=\"*"\
--set filters.service=\"*\" --set filters.deployment=\"*"\
Note: Filter expression in helm command must be escaped using backslash while using wild card * to exclude all resources
The setup wizard provides the configuration and installation commands for the applications needed for monitoring, CollectorSet-Controller, and Argus. For more information, see Argus Installation.
This step of the setup wizard does not display if LM Service Insight is not enabled in the account.
You have the option of configuring Services for specific Kubernetes label key-value pairs. Each key-value pair you add to the table will result in a new Service that groups together all Pods and Nodes with that label assigned. Metrics will be aggregated across these grouped Pods and Nodes to provide monitoring for overall health based on that label.
New Pods and Nodes will be automatically incorporated in the Service, and terminated Pods and Nodes will be automatically removed. The aggregated Service-level data will persist regardless of changes in underlying resources.
When setup completes, you’ll see a notice for a new Resource Group, Collector Group, and Dashboard Group.
The Resource Group representing your cluster dynamically groups Nodes based on worker role, and Pods and Services based on namespace:
Data is automatically collected from the Kubernetes API for Nodes, Pods, Containers (which are automatically discovered for each Pod), and Services. Additionally, standard applications will be automatically detected and monitored with LogicMonitor’s existing LogicModule library (based on AD for existing modules).
Note: Now even a non-admin user can add Kubernetes clusters. For more information, see Adding Kubernetes Cluster into Monitoring as Non-Admin User.
In This Article