LogicMonitor v.160 is scheduled to roll out to customer portals from October 25 through November 8.
Updated on 11/05/2021
An update for v.160 has been released and includes the following additional bug fixes:
- Fixed an issue that caused an extra backslash to be added to an instance name when WMI instances were added to the WinVolumeUsage- DataSource.
- Fixed an issue that caused the volume capacity DataSource to add an extra backslash to newly discovered instances added via Active Discovery.
- Fixed an issue that prevented instances discovered via Active Discovery from being added to the VMware_vCenter_VMDiskCapacity DataSource.
- Feature Highlights: Added the ability to edit OpenMetrics DataSources in the wizard.
- General Updates: Added enhancements to the information captured in Audit logs, support for new NetScan scheduling options, and fixed various bugs in Alerts, Cloud Monitoring, and the user interface.
- Updated Monitoring: Various fixes and enhancements to LogicModules for Cisco, Microsoft Active Directory, VMWare, and more.
OpenMetrics DataSource Editing
You can now edit OpenMetrics DataSources via the wizard instead of just in the standard DataSource editor. This allows you to update DataSources after creation using all of the wizard options and audits. When selecting the Edit icon, a window is displayed with the option to edit in the wizard or the LM Exchange editor.
OpenMetrics is a feature of LogicMonitor APM which has been available in a limited release capacity for the past few months. We are now getting ready to expand access with the launch of our Lighthouse Program for users that want access to our APM capabilities. If you are interested in participating in our Lighthouse Program, please fill out the Google form here.
- After clearing the Alerts table, a search for alerts now correctly displays the message, “No alerts match the current filters” when there is no match.
- Fixed an issue where alert notes were being overwritten if there were multiple API calls made to update the notes too close together.
- Audit logs for changes to alert thresholds at the DataSource level now include details such as datapoint name, datapoint ID, old value, and new value. This enhancement will be implemented for audit logs at the group and instance level in upcoming releases.
- Audit logs now include details about failed login attempts and prompts for a captcha code after five failed attempts.
- Audit logs for Scheduled Down Time (SDT) now include details of IDs when they are updated, deleted, added, removed, and stopped.
- Audit logs for deleted DataSources now include the DataSource ID. This ID was already captured when adding and updating DataSources.
- MAB protected VMs are now filtered out when requesting status for monitored VM backup jobs, to prevent error and inaccessibility of all backup job statuses.
- Argus v6 was released on September 15, 2021 and we’ve updated the upgrade instructions. For more information, see Argus v6 upgrade instructions.
- Argus cluster names are now restricted to 30 characters to ensure dashboards are created successfully. There is a 64-character limit to dashboard titles and by default Argus adds the prefix “Kubernetes Cluster:” and suffix “Dashboard” to dashboard and dashboard group titles.
- If a remote session fails to connect to an IP address, the Collector now retries with the hostname.
- Added warning messages to notify when PropertySources and Active Discovery fail.
- NetScans support new scheduling options. When scheduling Monthly (on a specific day), you have options to ensure that NetScans will run in the correct month if the month is shorter than the selection: (29 or Last Day, 30 or Last Day, 31 or Last Day). When scheduling Monthly (on day of week), you can select Last to run the NetScan during the last week of every month. These changes will apply for new NetScans scheduled or updated after this release and will not affect existing NetScans.
- To ensure both SAML and a normal user creation is consistent, user First Name and Last Name fields now only support space, @ and . special characters. Existing users with special characters outside of those allowed will still be able to log in, but validation will be enforced for any user updates.
- You can now view committed devices, config devices, and services on the Account Information page.
- Added a Test Script button for property-based TopologySources. You may find this useful for viewing relationships that would be discovered when building your own TopologySources.
- Fixed an issue where the Add other monitoring option for processes incorrectly sent the PID instead of the process name to WinProcessStats-.
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.
There are no new LogicModules in this release.
Updated the alert for the Lockout Duration and Lockout Observation Window to reflect Microsoft guidelines.
Resolved a bug that caused some instances to change names on Active Discovery due to auto property use in wildalias.
Instance name fallback logic now uses fixed string instead of auto property. This change will cause historical data loss for instances that were using the auto property in the name.
Ensures consistent collection and includes code cleanup.
Updated instance description to use “.184.108.40.206.220.127.116.11.18.104.22.168.1.2” OID which provides more detail.
Fixed minimum value for presenceStateAlert datapoint.
|(1 DataSource, 1 PropertySource)
Ensures port count calculation is consistent. Added MongoDB default port to probed ports.
Reduced SNMP walks when discovering Cisco entity data.
Updated the AppliesTo to target cloud devices with an existing Collector.
Added support for HyperV on Azure HCI devices: tags Azure HCI devices and enables monitoring.
Added sanitation for wildvalues to correct errors on data collection.
Fixed date parsing error.
Added new datapoints for dropped packets.
Uses correct runtime calculations for hosts running Windows 2012 R2.
Improvements to network type determination.
|(1 PropertySource, 1 TopologySource)
Prevents edge case involving Fortigate switches peering with Cisco routers.
When creating a JDBC connection string with a port number the parameter instanceName is ignored. Removed the instance name and added a test for internal SQL @@servername and the instance name to match. This only changes on multi-instance SQL with ports for each instance.
There are no deprecated LogicModules in this release. For the list of LogicModules deprecated over the past 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.
MGD Collector 30.001 release postponed
The automatic upgrade to MGD Collector 30.001 which was scheduled for deployment on October 27th has been postponed. An updated schedule will be provided in a future release.
No action is required at this time although you may upgrade to MGD Collector 30.001 on your own schedule. For more information, see the MGD Collector 30.001 release notes.
LogicMonitor APM Lighthouse Program
LogicMonitor APM has been available in a limited release capacity for the past few months. We are now getting ready to expand access with the launch of our Lighthouse Program for users that want access to our APM capabilities.
Along with early access, qualified customers and prospects will have the opportunity to influence the early direction of our product and provide feedback to enhance our APM offering. If you are interested in participating in our Lighthouse Program, please fill out the Google form here.
Upcoming enhancements for LM Logs
LM Logs will be changing over the next few releases with exciting new features that include query language support and other filtering options. You may notice things look a little bit different, but we assure you that no functionality is being removed. For more information, be sure to check the release notes for v161 and be on the lookout for documentation on the LogicMonitor website.