Our latest release comes with a new public IP address range. If your firewalls don’t support DNS based rules, be sure to update your whitelist to include this new range. Then, check out the other minor improvements we rolled out through late September as a part of v.110.
- Standardized detail in audit logs. Audit logs now standardize the display of both the name and ID of permanently deleted or restored devices or groups in the “Description” column.
- New public IP address range. A new IP address range has been added to LogicMonitor’s list of public IP addresses to which your firewall should allow access: 220.127.116.11/26. If you are whitelisting all IP addresses (vs. whitelisting the DNS of *.logicmonitor.com), please update your whitelist to include this public IP address range. For more information on LogicMonitor’s public IP addresses, see LogicMonitor Public IP Addresses and DNS Names.
- New “Last 30 days” filter for Collector update history. A new predefined time range filter of “Last 30 days” is now available when viewing the update history for a Collector. This new predefined time range allows users to more conveniently span the gap (without the need for defining a custom time range) that previously existed between the predefined time ranges of “Last 7 days” and “Last calendar month.”
- Alert List widget improvement. Previously, if a user was in the process of resizing a column in an Alert List widget, all column settings were lost if the widget underwent an auto refresh. LogicMonitor now prevents Alert List widget auto refreshes from occurring while its columns are being resized.
- Custom Graph widget improvement. In some instances, cloned Custom Graph widgets were not properly applying token values. This has been corrected.
- More proactive warning when instances are impacted by removal of local Collector-based monitoring. Building upon an enhancement released last month with v.109, a warning will be displayed upon any save to your cloud account when one or more instances are impacted by the removal of local Collector-based monitoring. Previously, this only happened when local Collector monitoring rules were edited. This improvement was made to make it easier to remove local Collector monitoring for EC2 instances and Azure VMs, without risking accidental changes resulting in historical data loss.
- Assignment of system.cloud.autodeleteon property. Cloud resources marked for deletion due to a tag filter change (i.e. the filter is restricted such that it no longer matches instance(s) already in monitoring) were not being assigned the system.cloud.autodeleteon property. This has been corrected.
- Improved URL parsing for monitored websites. When configuring the root URL of a Web Check, LogicMonitor now employs additional intelligence to (1) auto-remove all characters entered after the root URL (e.g. trailing slash, bookmark, query string, etc.) and (2) auto-assign “https://” or “https://” depending upon the root URL provided. The former enhancement is intended to reduce the occurrences of “Invalid Domain” errors and the latter to improve user workflow.
- Cisco Power Supplies – 1 DataSource
- Deprecated “CiscoPowerSupply-” in favor of “Cisco_System_PowerSupplies” as some Cisco models are reporting incorrect instance name formats which prevent proper data collection and alerting
- Dell_Networking – 1 ConfigSource
- Enabled debug logging with separate log files for each configuration instance
- Fortinet FortiOS – 1 ConfigSource
- Added more config line detection cases
- MS SQL – 1 PropertySource
- Added troubleshooting steps and a link to support documentation
- PaloAlto_FW_CLIConfigs -1 ConfigSource
- Added a debug logging option to collection script. AD script does not include ‘synced’ instance if HA mode is disabled or cannot be determined
- CiscoIOS – 1 ConfigSource
- Updated to handle prompt embedded in Expect config output
- IPMI Status Sensors, IPMI Full Sensors – 2 DataSources
- Added timeout to prevent AD running indefinitely in some cases
In this Article: