Container security best practices recommend running Docker containers as non-root users with the minimum necessary privileges to perform their intended tasks. This helps to limit the impact of any security breaches and makes it easier to manage and secure your Docker environment. By following the best practices, users can now run the LM Container collector … Continued
What is Container Monitoring? What are the advantages of Container Monitoring? LM Container provides organizations insight into the performance of applications running in containers and the health of the underlying container resources and orchestrating components. To get the most out of deployment, LogicMonitor presents these insights alongside your organization’s existing monitored hybrid infrastructure in a … Continued
By default, Argus deletes resources immediately. If you want to retain resources, you can configure the retention period to delete resources after the set time passes. You must configure the following parameters in the Argus configuration file: Note: The maximum retention period allowed for all resources is 10 days. If you want to retain resources … Continued
kube-state-metrics (KSM) monitors and generates metrics about the state of the Kubernetes objects. KSM monitors the health of various Kubernetes objects such as Deployments, Nodes, and Pods. For more information, see kube-state-metrics (KSM) documentation. You can now use the kube-state-metrics-based modules available in LM Exchange in conjunction with the new Argus and Collector Helm charts … Continued
Argus discovers all Kubernetes resources that are monitored by LogicMonitor. In addition, you can use Argus to exclude resources from monitoring. You can add resource filters in the Argus configuration files under the filter parameters. The rule engine evaluates rules sequentially; when the first rule is met and is evaluated as true, the rule engine … Continued
Argus is a tool for monitoring Kubernetes with LogicMonitor. Argus runs as a Pod in your cluster and uses LogicMonitor’s API to add Nodes, Pods, Services, and resources into monitoring. Once in monitoring, data collection starts automatically. Argus uses Kubernetes API to collect data for all monitored resources. Additionally, you can leverage LogicMonitor DataSources to … Continued
Configuring Collectorset-Controller using Helm Charts The Collectorset-Controller Helm chart supports the following values:Required Values Parameters Description accessID (default: “”) The LogicMonitor API key ID accessKey (default: “”) The LogicMonitor API key account (default: “”) The LogicMonitor account name Optional Values Parameters Settings Parameters Description imageRepository (default: “logicmonitor/collectorset-controller”) The image repository of the Collectorset-Controller container imageTag … Continued
With Argus v5 or the previous resource tree, dynamic groups were created for each type of resource. Now with Argus v7, the resource tree is enabled by default, to optimize the performance. In the new resource tree, all the namespace scoped resources such as Pods, Deployments, and Services are grouped under Namespaces, and cluster scoped … Continued
When you add your Kubernetes cluster into monitoring, dynamic groups are used to group the cluster resources. For more information on adding a Kubernetes cluster into monitoring, see Adding Kubernetes Cluster into Monitoring. Earlier, for adding dynamic groups, you required ‘manage all resources’ permission. However, now you can use API keys that have access to … Continued
Google Anthos enables you to run and manage Kubernetes Clusters running anywhere, whether natively via Google Kubernetes Engine (GKE) or externally in another cloud service and on-premise. With LM Container, you can ensure central and consistent monitoring for clusters managed through Anthos. Specifically, LM Container provides a central view within LogicMonitor for you to monitor … Continued