LogicMonitor v.176 is scheduled to roll out to customer portals from September 26 through October 5.
- Feature Highlights: New LogicMonitor API v3 release. New Collector Release. Multi-SSO support.
- General Updates: Added new resources to Kubernetes topology maps, added new dashboards for tracking pod and node metrics, improved monitoring for Azure Site Recovery, added support for Azure accounts in China Regions, and more.
- Updated Monitoring: Released new modules to monitor Azure emerging issues, to add topology coverage for Kubernetes, and use OAuth for Office 365 Exchange Online users.
LogicMonitor API v3 Release
LogicMonitor REST API v3 is now available for use. The REST API Swagger documentation contains 203 frequently used API endpoints. This release also includes a Python SDK file. For more information, see Using LogicMonitor’s REST API.
GD Collector 32.003 Release
GD Collector 32.003 was released on September 20, 2022. This is a patch release to fix a collector upgrade issue. For more information, see GD Collector 32.003 Release Notes.
EA Collector 32.400 Release
EA Collector 32.400 was released on September 20, 2022. For more informations, see EA Collector 32.400 Release Notes.
New Multi-SSO Support
LogicMonitor’s Multi Sign-On solution enables administrators to add multiple tenants (IdPs) and manage users directly from their Identity Provider (IdP). For more information, see Multi Sign-On.
- You can now manage datapoint threshold levels at the instance group and instance level. By default, new instances inherit the properties of the instance group.
- You can now see several new resources such as Jobs, Deployments, and ReplicaSets in your Kubernetes topology map.
- Updated the cluster overview dashboard to include resource usage charts such as CPU and Memory used by the pods and the nodes in the cluster.
- Added new dashboards for tracking pods and nodes metrics.
- Updated Cloud Common Library to 7.0.0.
- Added BurstBalance to the AWS_RDS datasource.
- Added monitoring for replication lag time for Azure Site Recovery.
- Made improvements to the Azure Recovery Protected Items auto properties.
- Added basic properties for data backups and recovery in Azure.
- Added support for data collection and monitoring in Azure China regions. These regions will only be available for accounts that are valid in China and have a China Subscription ID.
- Added support for discovering and monitoring AWS Transfer Family servers using the LM AWS Integration.
- Corrected handling of BytesReceivedRate in Microsoft_Azure_NetworkInterface datasource to correctly show the data.
- Fixed an issue that prevented Azure Databricks were from being discovered or monitored.
- Fixed an issue where the Basic Info fields were not populating for AWS and Azure Info tabs.
- For auto-deleted cloud resources, alerting is now disabled before deletion to ensure that open alerts clear, rather than remaining open with no closure options after the resource is deleted.
- You can now create log pipelines and log alert conditions from the logs action menu. For more information, see Log Processing Pipelines and Log Alert Conditions in the product documentation.
- You can now use a Stop button on the Logs page to stop long-running queries. For more information, see Logs Query Language.
- Log pipeline queries did not generate log alerts if the query included a resource group.
- LogSources did now import from the repository when safe import was disabled.
- Unmonitored hosts associated with a Netscan execution are now removed when the execution record is removed. Previously, other delete actions would unexpectedly fail due to the lingering unmonitored host records.
- Fixed the issue where GET/santaba/rest/alert/alerts endpoint displayed inconsistent results. For more information, see Using LogicMonitor’s REST API.
- The output from the Zoom Room API is now stored in Redis cache, which resolves the 429: too many request error that was occurring.
- When clicking Explore Maps from the Maps tab in a Resource page or viewing the Maps tab on individual alerts, your context and map progress is now saved. This makes it easier to troubleshoot with the topology map when using an alert as the entry point. Previously it would reset when navigating to the main mapping canvas from one of these tabs.
- The Mapping page now shows more information about each saved map and makes it easier for you to quickly switch between saved maps. For more information, see Saved Maps.
- You can now view port-level information on the topology map when clicking on Network-type edges. For more information, see Interface Mapping.
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 ConfigSource using OAuth to monitor users.|
For related ConfigSource updates for for Office 365 Exchange Online, see Updated LogicModules.
Azure Emerging Issues
|New EventSource for Azure emerging issues.|
|New topology coverage for Kubernetes owner references.|
|Removed duplicate code.|
|Updated authentication to use app-only authentication in accordance with Microsoft’s October 1st cutoff for basic authentication. For more information, see Microsoft’s Set up app-only authentication documentation.|
|Removed datapoint FreeStorage due to inconsistent results. A new datapoint will be added in the future when consistent results can be achieved.|
|Added new datapoints for monitoring BurstBalance.|
|Fixed a bug that prevented data collection for devices with a certain uptime.|
|Improved session handling in collector script cache and additional debug messages. Now checks the expiration time of the cache entry for the UCS session and will proactively log out and get a fresh session when expiry will occur in less than 5 polling cycles. We highly recommend all customers using this module upgrade collectors to version 32.200 or higher which contains persistent script cache and will have less chance of losing sessions due to script cache volatility.|
|Explicitly set enable HTTPS property to Boolean.|
|Improved error handling and messaging for easier debugging.|
|Added handling for *0 values in command line output. Expanded state table for physical disks.|
|Updated to handle new script cache objects.|
|Updated queries, instance names, and datapoints.|
|Corrected datapoints to be metric type gauge instead of counter.|
UPS Output Lines-
|Updated graph to display amps in correct scale.|
|Added Disconnect-VBRServer to the end of all scripts.|
|Replaced new lines with a space in descriptions. New lines are not supported in descriptions or ILPs and will prevent ILPs from being set when present.|
|Fixed parameter issue in function call.|
|Updated description to clarify admin requirements.|
|Improved mapping for Cisco Nexus switches with CDP neighbors using a custom property (cisco.vpc) for Cisco VPC case when unable to autodetect using Cisco-VPC-MIB.|
|Added LLDP sysname ERI setting for Palo Alto active/passive connections.|
|Fixed a bug in the logic that determines whether to use integrated security.|
|Updated the ERT for proper map icons.|
|Improved the label selector.|
|Deduplicated bridge entries and unindexed Cisco bridge entries to prevent multiple bridge MAC links.|
The following 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. For the history of deprecated modules, see Deprecated LogicModules.
|Details||End of Support Date|
|LogicMonitor deprecated the recently released PaloAlto SDWAN package because it failed to meet our quality standards.|
Recommendation: Use LogicMonitor’s native SNMP capabilities to monitor Palo Alto Network Prisma SN-WAN Instant-On (“ION”) devices (formerly Cloudgenix).
LogicMonitor is actively assessing how to leverage Palo Alto Networks’ Unified SASE SD-WAN API to deliver complementary, additional monitoring value to Prisma SD-WAN customers and partners.
|September 22, 2022|
|Sharepoint does not support the new required app-only authentication.||September 30, 2022|