v.186 Release NotesLast updated on 03 May, 2023
LogicMonitor v.186 is scheduled to roll out to customer portals from April 24, 2023 through May 1, 2023.
Updated on May 3, 2023
- Setting alert thresholds at the instance level does not save the threshold at the group level. Newly discovered instances do not inherit the threshold as expected.
- Feature Highlights: Monitor Azure costs using custom tags.
- General Updates: Added support for Zoom OAuth in the LogicMonitor integration for Zoom, updated ConfigSource and TopologySource editors, added preservation for changes to alert thresholds when updating modules, and more.
- Updated Monitoring: New modules to monitor Kubernetes Scheduler and more.
Note: The LogicMonitor platform is restricting access in limited regions of the world to comply with US trade sanctions and export control laws. All affected customers have been notified of this restriction several months in-advance. If you are impacted, you can contact LogicMonitor Compliance to request an exception from LogicMonitor to resume access to the LogicMonitor service.
Azure Cost Management by Tag
You can now use custom tags (such as application, environment, createdBy) to monitor your Azure spend and identify opportunities for optimization. If you are using the Azure Rate Card Cost By Tag datasource, you will need to move to the Azure Cost Management datasources by the end of June. For more information, see Azure Billing Monitoring in the product documentation.
- When adding a new AWS Account to LogicMonitor, you can now specify the location for the dashboards.
- Added support for Zoom OAuth for authenticating the LogicMonitor SaaS integration for Zoom. You must update your existing Zoom SaaS integrations to use this OAuth support before June 2023, when Zoom will retire the existing JWT authentication. For more information, see Updating Existing Zoom SaaS Monitoring to OAuth.
- Added support for discovering and monitoring Azure Front Door Standard/Premium SKU (CDN profiles).
- Added support for monitoring VPN Connections within an Azure VPN Gateway.
- Added support in GCP monitoring for regional and internal HTTP/HTTPS load balancers.
- Fixed an issue where data collection on VMs did not resume when the VM transitioned from a stopped state back to a running state.
- You can now monitor Kubernetes scheduler. Kubernetes scheduler watches newly created pods in the system and finds the best pod that they could run on.
- You can now preserve changes to alert thresholds when updating customized modules in My Module Toolbox. Previously, this was not a preservation option.
- Updated metatdata associations that previously caused incorrect metadata to be shown in some cases.
- Updated ConfigSource and TopologySource editors to use the New UI workflows in My Module Toolbox. For more information see the following articles in the product documentation:
- Only non-administrative users have permission to generate API tokens. If you are a user with an administrator role, you will see a warning message if you try to create an API token.
- Fixed an issue where Dynamic Maps were not obeying RBAC settings.
- Updated the topology core icons to improve the user interface response times.
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 to monitor Azure Cost by Tag.|
|New module to monitor Kubernetes scheduler.|
|Added support for a config.hostprops host property to specify an alternate host name for Common Configs to attempt collection from.|
|AWS Billing costs are modeled with decimals having a scale of 10 digits. Previously LogicMonitor was capturing the billing costs with a scale of 4 digits, which could lead to less accurate cost monitoring. This update includes support for 10 digits to the right of the decimal for AWS Billing Cost data sources.|
|Default SNMP timeout for AD and collection scripts set to 20. The optional property cisco.ipsec.aggtun.timeout can be set to the requested amount of seconds.|
|Changed the exception type that the AD try/catch logic was looking for.|
|Added missing quotes on hostProps for Cisco_Transceiver_Sensors|
|Updated the description of Citrix_XenApp_UserExperience datasource.|
|Updated to ensure that credentials do not print to logs.|
|Updated diskio_bytes_read and diskio_bytes_write datapoints to read from the proper response field.|
|Set debug mode to false.|
|Modified appliesTo to exclude K8s managed service provider (eks, aks and gke).|
|Added Status graph to Helm Status DS along with a Datapoint to monitor unknown status of Helm Release.|
|Fixed an issue with the implementation not fetching data.|
|Added null check in LLDP_Neighbors/ad.groovy.|
|Updated description of Microsoft_Azure_BackupJobStatus to make it clear that the DS only pulls 7 days of history for Backup Jobs.|
|Microsoft_Azure_SQLDatabase and Microsoft_Azure_SQLDatabaseNonDTU will now take into consideration the SQL Database’s edition when determining whether the SQL Database is DTU-based or not.|
|In Active Discovery, allow “passThrough” and “ptTunnel” tunnel instances.|
|Implemented retry logic and hardcoded lookback period to 10 minutes to improve collection performance due to API limitations.|
|Fixed detection of Argus KSM while using lm-container charts in case of multiple kube-state-metrics installations being present in cluster.|
|Corrected typo in appliesTo preventing proper device matching for Dell PowerConnect devices.|
|This update includes the following changes:|
* Added new property for SQL version and edition.
* Added checks to prevent failure when WMI times out.
* Will check for existing instances and preserve them if they work.
* Changed the connection string to add encryption (
* Updated processing of the mssql.deletenames resource property.
|Added support for custom properties “topo.timeout”, which applies to Networking_L2_snmpSwitch SNMP calls without a specific timeout (default 30000 ms) and “topo.interfacesTimeout”, which applies to the Networking_L2_snmpSwitch SNMP interface walk (default 10000 ms). Added documentation for custom “topo.” properties to tech notes.|