v.185 Release NotesLast updated on 11 April, 2023
LogicMonitor v.185 is scheduled to roll out to customer portals from April 10, 2023 through April 17, 2023.
- Feature Highlights: New dashboards for AWS and Azure monitoring. Report sharing for authenticated users. Cumulative monthly usage reporting. Enhanced user interface and new latency graph overlay for Tracing.
- General Updates: New workflow for creating JobMonitor modules; support for discovering and monitoring Azure VPN Gateways and Azure Virtual Hubs; updates to API User permissions; and more.
- Updated Monitoring: New modules to monitor AWS Route 53 Hosted Zones and more.
New AWS and Azure Dashboards
We’ve published 20 new out-of-the-box AWS and Azure dashboards! These dashboards highlight key metrics and provide useful service-specific views for understanding service health, performance, and availability. These dashboards populate automatically for new cloud accounts added into LogicMonitor. For existing accounts, you can find the dashboard definitions in our AWS GitHub repository and Azure GitHub Repository and import the JSON file into directly into your LogicMonitor account. For more information, see Importing Dashboards in the product documentation.
Report Sharing for Authenticated Users
You can now secure your shared reports to only be available to logged-in users. If the “Allow Shared Reports” toggle is set to No in your portal, your reports will only be available to users that have an account. For more information, see Accessing and Sharing Generated Reports.
Disclaimer: This feature is currently in Open Beta. You can submit feedback about this feature directly in your LogicMonitor portal using the Support Resources. For more information, see Accessing Support Resources in the product documentation.
You can now view the cumulative monthly usage for your organization to help you understand how and where your environment is incurring the most data usage. You can view summaries of this information directly in your LogicMonitor portal using the available visual components. You can view the total cumulative usage for your selected product in a month-to-date usage summary view and in a graph format, and view a list of the areas in your portal with the top usage. For more information, see Usage Reporting in the product documentation.
New Tracing Latency Graph Overlay
You can visually compare a single span’s data for two different time ranges on the latency graph. On selecting the required time ranges for the span data, you will see an overlay graph of two different colors displayed. These colors indicate the two different time ranges selected. If there are any errors for the selected time ranges, they too will appear in different colors. For more information, see Viewing Traces Data.
Enhanced User Interface for Tracing
The user interface for Tracing is now more straightforward and intuitive. It displays information like the application topology map of your services, error rate, average latency, and request rate of your services through different widgets. Additionally, using one click you can filter the data based on either latency or time period. For more information, see Traces Page Overview.
- Added support for discovering and monitoring Azure VPN Gateways and Azure Virtual Hubs as a part of the Azure Virtual WAN service
- Corrected the values for the onPremisesSyncEnabled datapoint in the Microsoft_Azure_ActiveDirectorySync dataSource.
- Fixed an issue where gaps were observed in Azure graphs because of metric-level throttling by the Azure API.
- Fixed an issue where Azure Service Health alerts were not properly displaying special characters, such as quotes.
- Fixed an issue to ensure that Azure network interfaces associated with private endpoints will not be discovered by default, because such network interfaces don’t expose metrics and result in 404 errors.
- Fixed an issue where GCP DataAnalytics Dataflow was not showing data.
- Added support to view or track the changes made to the ConfigSource. You can view the changes by navigating to Resources > select the ConfigSource> select the config check > History.
Note: The History tab is displayed in the Alert Tuning Config Slots section. For more information, see Instance Level Thresholding.
- New UI workflow for creating JobMonitor modules. For more information, see JobMonitor Configuration in the product documentation.
- The Import From Repository URL will no longer include the version specifier when updating modules.
- An API User with Administrator-level permissions, which allows complete access to your portal, will no longer be able to create API Tokens (LMv1 and Bearer). This change ensures that your portal is protected in case an API token is compromised. An Administrator can assign other API Users the ability to create API tokens by checking Allow Creation of API Token under Settings > User Profile. Existing API tokens that were created by an administrator user will continue to work. For more information, see API Tokens in the product documentation.
- Fixed an issue where Dynamic Maps were not obeying role-based access control (RBAC) restrictions.
- Fixed an issue where Node Icons were getting replaced with white squares for large maps in some scenarios.
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 AWS Route 53 Hosted Zones.|
|Updated Configsource to output dates in UTC time code. This handles erroneous error messages on the date the clock changes for daylight savings time.|
WARNING: Installing this datasource may result in a new configuration change alert being issued.
|Further restricted appliesTo to prevent device matches where required SSH credentials have not been configured.|
|Added new metric to AWS_Route53 datasource.|
|Added log out routines to the Cisco APIC modules along with some debug messages.|
|Fixed an issue in the variable type.|
|Fixed description for datapoint onPremisesSyncEnabled to reflect status mapping correctly.|
|Removed unintended alert on TotalGetRequests.|
|Added differential backup age and size datapoints. Updated datapoint descriptions.|
|Eliminated scanning of all ports and instead limited processing to only the known active ports.|
|Fixed an issue with StatusTypes, which was reporting incorrect values for the Status datapoint. This was verified against Oracle documentation.|
|The module will now sum instances with the same name and Extended SNMP timeout. Added check for SNMP returning empty or invalid data. The datasource will continue to check other instances if one has bad data. This increases reliability of the datasource overall.|
|Modified the emit function to remove any unsuitable characters for the wildvalue, such as the backslash.|
|Added sanitation for wildvalues to replace invalid characters with underscores.|
|Updated appliesTo to more directly target applicable devices. Updated snippet loader to remove use of new GroovyShell for improved collector performance.|
|Added a filter for ambiguous commands to Aruba Common Configs.|
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. For the history of deprecated modules, see Deprecated LogicModules.
|LogicModule Name||Details||End of Support Date|
|Dell_PowerConnect_Interfaces was initially developed to address discovery-based indexing issues that were seen in PowerConnect environments that presented collection issues where duplicate interface descriptions existed. These issues have since been addressed in SNMP_Network_Interfaces which also includes stability fixes in larger environments.||2023-04-23|
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 Rate Card Billing Deprecation
Microsoft has deprecated Rate Card, and LogicMonitor will not support the Rate Card API after June 3, 2023. LogicMonitor recommends using the Cost Management API and the related LogicMonitor Cost Management DataSources.