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
LogicMonitor’s VMware NSX-T monitoring package leverages the VMware NSX-T Data Center API to monitor and alert on metrics for clusters, cluster managers/controllers, edges, firewalls, load balancers, and other virtualized NSX-T networking components. Compatibility As of January 2022, LogicMonitor’s VMware NSX-T package is compatible with NSX-T API versions 2.4 – 3.2. Note: This monitoring package may … Continued
LogicMonitor’s Silver Peak Orchestrator monitoring uses the Orchestrator REST API to monitor Silver Peak SD-WAN deployments, as well as individual Silver Peak appliances. Compatibility LogicMonitor’s Silver Peak Orchestrator package is compatible with Orchestrator REST API version 8.3. For compatibility with 9.x versions and to follow HPE Aruba Networking best practices, consider migrating to the HPE Aruba … Continued
LogicMonitor’s Jenkins monitoring package leverages the native Jenkins API and Metrics API plugin to monitor and alert on the status of builds as well as server system stats. Technology Type Compatibility As of December 2021, LogicMonitor’s Jenkins package is compatible with: As Jenkins releases newer versions of these, LogicMonitor will test and extend coverage as … Continued
LogicMonitor offers monitoring for Apache Hive by default. The monitoring suite uses JMX to query Apache Hive for a wide variety of health and performance metrics. Requirements Apache Hive version 2.3.8 or higher must be used. Adding Apache Hive Resources The following custom property must be set on the Apache Hive resource within LogicMonitor. For … 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