LogicMonitor v.168 is now scheduled to roll out to customer portals from April 11 through April 20.
Updated on 04/21/2022
- Fixed an issue that prevented reports from being generated for some users.
- Feature Highlights: Added a new Log Field panel to LM Logs and non-admin users can now add Kubernetes clusters into monitoring.
- General Updates: Added several enhancements to LM Cloud and SaaS monitoring, added a new Node Properties tab to the Mappings page and Maps tab, and more.
- Updated Monitoring: Added monitoring for AWS Lambda Insights, AWS OpenSearch, Salesforce license usage, and more.
Non-Admin Users Can Now Add Kubernetes Clusters
Users without the “Manage All” permission can now add Kubernetes clusters to LogicMonitor. For more information, see Adding Kubernetes Cluster into Monitoring as Non-Admin User.
New Log Field Panel in LM Logs
You can now view the list of metadata and parsed fields and their values from the new Log Fields panel in LM Logs. Fields can be expanded to show the top 10 values with the ability to add filters to the query bar. You can also add and hide field columns in the Logs table and move columns around based on user preference.
- Added a new SaaS Lite integration for Snowflake. You may find this useful for monitoring and alerting on Snowflake availability and status from within LogicMonitor.
- Added the Run Active Discovery option to the Manage menu for SaaS integration resources. You may find this useful for testing for instance discovery and ensuring successful data collection in a more timely manner.
- Added Status monitoring for Microsoft Office 365, Zoom, and Salesforce. Status monitoring enables you to get visibility into the availability of Microsoft Office 365, Zoom, and Salesforce services alongside the rest of their infra + apps. This new functionality enables you to both minimize business disruption and to have visibility into affected services/platform areas/regions when service is disrupted, helping empower employee productivity.
- Added Salesforce License monitoring. Without insight into license consumption, IT teams are in the dark about their license consumption, which can lead to overages if left unchecked. Keeping track of total vs. used licenses allows Salesforce admins to proactively monitor license consumption, which can help ensure that there are no overages and helps in contract negotiation with Salesforce.
- The following properties have been added to Lambda functions to enable additional monitoring where Lambda Insights is enabled:
- aws.layers—Lists the Lambda layers
- aws.lambdaInsightsEnabled—Returns “true” if the function has Lambda Insights enabled.
- You can now monitor your Azure costs within LogicMonitor; organized by Subscription ID, Region, and Service for CSP and EA subscriptions. For more information, see Azure Billing Monitoring.
- Fixed an issue that prevented the Microsoft_Azure_VirtualDesktopSessionHosts DataSource from collecting data correctly. In addition, the Active Discovery schedule for this DataSource was updated to 1 hour.
- Fixed an issue that prevented data from being populated for ‘AzureIaaSVM’ backup types in Azure Recovery Services.
- Selecting a time range on the LM Logs page now runs log queries automatically.
- Removed dependency on the component status API (deprecated since Kubernetes v1.19) for health checks of etcd, kube-controller-manager, and kube-scheduler. It is recommended that you use the latest version of the Kubernetes_ControlPlane module to avoid warnings during installation.
- Kubernetes resources now have dedicated icons to help identify them in the Resource tree.
- Improved the performance of the Kubernetes Control Plane module.
- To enable successful installation, the ClusterGroupId property now defaults to 1 if invalid values are specified for the Helm chart parameter.
- Fixed an issue that prevented users from installing Collectorset-Controller on Kubernetes clusters v1.19 or earlier.
- Fixed an issue that prevented filtering based on numerical values for alerts.
- Netscan policies can now be individually configured to include or exclude network and broadcast addresses when scanning CIDR ranges.
- Added the ability to auto-instrument .NET applications via the Traces onboarding wizard.
- Fixed an issue that prevented users from resetting their passwords when viewing LogicMonitor on a mobile device.
- Added the Node Properties tab to the node details panel on the Mappings page and Maps tab.
- You can now enable Root Cause Analysis (RCA) for virtual machine resources.
PagerDuty Integration Enhancements
If your environment uses the PagerDuty integration, and you are currently using the V2 webhook extensions, you can now upgrade your integration using the LogicMonitor portal. For more information about the timeline of PagerDuty webhook versions, see PagerDuty’s Webhooks documentation.
You can upgrade this integration directly in your LogicMonitor portal by modifying the PagerDuty integration settings to use PagerDuty’s V3 Webhook subscriptions. For more information about upgrading your PagerDuty integration, see the “PagerDuty Integration Upgrades” section of the PagerDuty Integration support article.
New and updated LogicModules are available for you to import from the LogicMonitor Public Repository. This section lists the LogicModules that are new in this release, updated in this release, or will be removed in a future release. Changes related to the LogicModule feature will be listed under General Updates.
|New modules for expanders and compact flash.|
|New topology coverage for NSXT devices.|
|New modules for Otel Collectors used for push metrics DataSources.|
|(1 DataSource) |
|Added new Linux Pressure Stall Information monitoring using SSH.|
|New module to flag devices with the updated NTP version.|
|New module for monitoring AWS Lambda Insights.|
|New module for monitoring AWS OpenSearch.|
|Added monitoring for Salesforce license usage.|
|New module for monitoring PosgreSQL in Azure.|
|New module for meeting quality of service on Zoom SaaS integration.|
|New module for monitoring container insights task family.|
|New Azure monitoring for cost by subscription.|
|New Azure monitoring for cost by service.|
|New monitoring for Azure cost by region.|
|Made improvements to instance-level properties and removed fallback methods specific to old Collector versions that are no longer in circulation.|
|Updated to no longer attempt collection on IOS devices. By default, IOS devices attempt to connect to a host matching any unknown lines.|
|Updated module to make more small SNMP walks instead of one large walk to prevent timeouts for devices with a large number of instances.|
|(1 DataSource) |
|Fixed calculation for the SizeMinusEightPercent datapoint.|
|Added an alert for no data on status and ability to customize connection port with new host property docker.port.|
|Added null checks on descriptions to prevent script failure when descriptions are not present.|
|Added debug and log modes to script for ease in troubleshooting. Updated descriptions to correct units.|
|Fixed an issue that prevented clusters from being monitored.|
|Updated filters to better capture uptime entries and other lines that do not reflect config changes.|
|Increased the Active Discovery interval to once a day.|
|Fixed an issue that prevented data collection for the retransQueueSize datapoint.|
|Updated controllers to move expanders and compact flash to dedicated modules. New modules should be imported with updates to ensure these components are still monitored.|
|Updated module to filter out snapshots and added pagination support for large payloads.|
|Updated raw process query to exclude process ID 0.|
|Added support for API version 6.2 and allow for token-based authentication using host property “rubrik.api.key.”|
|Updated package to use new snippet loader for Collector performance gains when running in agent. Backwards compatibility is maintained so that Collectors with old loaders or running in SSE will not be impacted by updating.|
|Added additional graphs for better troubleshooting memory usage.|
|Added topology support for NSXT devices and connections.|
|Updated to display names and graphs.|
|Improved edge mapping for virtual machines and switches. SNMP_Network_Interface now supports making the new interfaces topology edges toggleable via the topo.mapinterfaces property.|
|Added horizon.hostname device property as the primary source for hostname with system.hostname used as a fallback to allow customers the option to customize which name is used in connection.|
|Updated AppliesTo so that only one of these modules will apply to a device depending on which NTP version they are using. Note: This is a history-breaking change. The new PropertySource should be imported first to ensure no gaps occur in NTP monitoring.|
|Reduced execution time by making smaller more targeted SNMP queries to prevent script timeouts.|
|Added clarification to the datapoint description for UptimeAlert and increased the alert clear interval to 24 consecutive polls to allow for 4 hours of alert visibility.|
|Corrected the percent_used datapoint to calculate from volumes rather than volumes + snapshots, as snapshots consume capacity from the array level.|
|Updated AppliesTo to restrict to only container insight devices.|
This table lists LogicModules that we are deprecating in this release. This means that these LogicModules will be removed in a future release. If available, a replacement LogicModule is listed.
|LogicModule Name |
|Details||End of Support Date|
|Updated to current conventions and now uses the Win32_PerfFormattedData_Counters_ProcessorInformation WMI class.||4/15/22|
For the list of LogicModules deprecated over the past five releases, see the support article Deprecated LogicModules.
In this section, you will find announcements about upcoming beta features, updates about ongoing beta features, and information about the end-of-life of existing features.
Azure China Regions Monitoring Beta
Beginning with v168, select users can opt-in and start monitoring their Azure China Cloud accounts. Contact LogicMonitor Support to enable this beta feature for your LogicMonitor portal. After the feature has been enabled, you must add a new Cloud account to be tied to your China-hosted region using the Cloud Account (Legacy) option and select the China account checkbox on the Permissions tab. On the Services tab, select the China regions you want to monitor. If you need additional assistance, contact LogicMonitor Support.
Old Alert Page Deprecation Notice
Support for the old Alert page (https://accountname.logicmonitor.com/santaba/uiv4/alert) has been removed. Issues related to the old Alert page are no longer being addressed and access to the page will be removed with an upcoming release.
To ensure that you are using the most up-to-date Alerts page, click Alerts in the LogicMonitor Navigation sidebar or append “/uiv4/alerts” to your LogicMonitor URL.