A representative will reach out shortly with next steps.
Questions on how to best use LogicMonitor?
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!
v.119 Release: Auto-Balanced Collector Groups & Topology Mapping
Last updated on 14 September, 2022
Rolling out through mid-May, LogicMonitor v.119 brings with it two exciting new features: Auto-Balanced Collector Groups and topology mapping. Read on for highlights of these new features, and details on other enhancements included in this v.119 release.
New Feature Highlight: Auto-Balanced Collector Groups
Get better device balancing, scaling, and failover with LogicMonitor’s brand new Auto-Balanced Collector Groups (ABCGs). An ABCG is a group of Collectors that share device load. ABCGs bring more efficient Collector management and monitoring through their ability to:
Dynamically move devices from one Collector to another within the ABCG in order to prevent any individual Collector from becoming over-subscribed
Equally distribute devices on a failed Collector to the remaining active Collectors in the ABCG
Streamline device creation by simply assigning an ABCG and letting the ABCG decide which Collector will perform the monitoring
A few days before the official rollout out of v.119 (on April 26 to be exact), we released topology mapping. Available to users of LogicMonitor Pro and Enterprise packages, LogicMonitor’s topology mapping allows you to visualize the logical relationships between elements in your network environment.
This additional context can be very beneficial to your monitoring operations, providing you with the ability to:
Discover and map relationships between resources
Generate topology maps based on alerts to streamline your troubleshooting workflow
Navigate resources based on topology relationships
Save relevant and frequently-used topology maps for monitoring continuity
Topology is auto-discovered by LogicMonitor! Once you’ve downloaded all necessary LogicModules, relationships are dynamically generated. To learn more, see Topology Mapping Overview.
Other v.119 Enhancements
Cleared alerts only filtering. When filtering alerts on the Alerts page (or Alerts tab), you now have the ability to see only those alerts that have been cleared. This is accomplished by checking the new “Yes” option available for the Cleared filter. Previously, you could only see cleared alerts in addition to active alerts (the “All” option) or explicitly exclude cleared alerts (the “No” option).
Amazon Web Services (AWS) monitoring updates:
Tag discovery filter for DynamoDB. Added a tag discovery filter for the AWS DynamoDB service. We will not be removing the previously implemented name filter; the new tag filter will be connected with a logical AND to the name filter. You may find this new tag filter useful for preventing DynamoDB tables from being discovered based on tags that already exist in your AWS environment.
AWS DMS replication instances monitoring. Added discovery and monitoring support for AWS Database Migration Service (DMS) replication instances.
Google Cloud Platform (GCP) monitoring updates:
UI text update for clarity. A term used in the text of the Add and Manage cloud account dialogs for GCP was updated to eliminate confusion. The dialogs now indicate that automatic disablement of alerting is available for deleted instances. Previously, the dialogs used the term terminated which, in GCP terminology, implies a stopped state.
Improved warning for manual deletion of Kubernetes resources. Added a more helpful warning when users attempt to delete monitored Kubernetes resources that are auto-managed by Argus.
LM Service Insight
Adding member graphs to dashboards. Service member (i.e. instance and device) graphs can now be added to dashboards as widgets directly from the Service’s Graphs tab. This new capability parallels that already in place for adding a resource’s graphs to dashboards. You may find this useful for quickly building dashboards for your Services.
Cleared-only alerts retrieval. The LogicMonitor REST API supports the new “Yes” option (added in this release) for the Cleared filter. This new option retrieves only those alerts that have been cleared. It is referenced in the API as cleared:true.
New debug commands. To support LogicMonitor’s brand new topology mapping capabilities, two new commands are now available in the Collector Debug Facility that allow users to debug issues related to the unintended existence of duplicate external resource IDs (ERIs):
!erimergelist [threshold=xxx] – This command lists all ERI values that appear across resources/instances (or those that meet a designated threshold if specified)
!erimergedetail <eriValue> – This command lists all the resources/instances bound to an ERI value
Edge collapsing. When multiple edges connect two vertices, the default behavior is to collapse those edges into a single edge for cleaner viewing. A new Display all edges option allows you to override this default behavior on a per-map basis from the map’s settings. Alternately, right-clicking on a collapsed edge will also show all edges between two vertices.
Capturing multiple vertices for dragging. In addition to dragging and dropping a single vertex into a new position within a topology map, you can now also move multiple vertices in a topology map at once. To do so, position the cursor in approximation to the desired vertices and hold down a left click until the cursor becomes a plus sign. Then, with the click still held, draw a box that encompasses all the vertices you would like to move. Click any one of the vertices that you drew a box over to drag all selected vertices to a new location.
LogicModules that have been added or updated since the last release.
New Monitoring Coverage
Cisco IPSec Tunnels – 1 DataSource
The existing Cisco IPSec Tunnels DataSource has been deprecated and removed; this new module is named with a slight variance (Cisco_IPSec_Tunnels) so as to not accidentally overwrite existing DataSource