LogicMonitor v.152 is scheduled to roll out to customer portals from May 12th to May 24th.
- General Updates: Added filtering based on alert status to LM Logs, improvements and fixes to onboarding for Cloud Integrations onboarding, the Alerts page, and more.
- Updated Monitoring: New LogicModules to monitor Microsoft Azure SignalR and NetSNMP memory usage.
- Looking Ahead: Push Metrics API, OpenMetrics DataSource wizard, and Distributed Tracing will be entering beta in an upcoming release. Find out more!
- ADDED functionality to save header graph selections as part of a “Saved View” for the Alerts page.
- ADDED alert sounds to the Alerts page. You can enable sounds for Critical, Error, and Warning alerts.
- CHANGED the default behavior when resetting time range and filter selection. The time range should be set to “Any Time” and all severity toggles should be enabled.
- FIXED an issue where it wasn’t possible to change the time range to view Anomaly Detection graphs associated with Alerts.
- FIXED issues where Datapoint name was missing or showed “null” in Audit Logs for resource and instance-level changes to Dynamic Thresholds.
- FIXED an issue where Audit Logs included information for datapoints even when they were not updated. The log should only contain information for the dynamic and static thresholds that are changed or updated.
- ADDED “Test AppliesTo” functionality for Cloud integrations where Local Collectors are applied.
- ADDED capability for users to clear Permissions warnings and errors for Cloud accounts when “Test Permissions” is clicked when managing and adding integrations.
- ADDED access controls to the Cloud Integrations page to display only Cloud and SaaS tiles that users have access to.
- CHANGED the Microsoft Azure configuration options to make the billing country an optional field.
- FIXED an issue in Azure accounts where users could not edit permissions for the account when the secret key expired.
- FIXED an issue where the setting to “automatically delete terminated resources” was not working.
- CHANGED the commands for adding the LogicMonitor Helm chart repository to use ‘github.io’ because GitHub has stopped redirecting from ‘github.com’. If you previously added LogicMonitor charts, you will need to re-add the charts with the ‘github.io’ command to avoid future Helm update failures:
helm repo add logicmonitor https://logicmonitor.github.io/k8s-helm-charts
- RELEASED GD Collector 30.000 on 29 April 2021. This version incorporates updates and fixes from GD 29.003 and EA 29.xxx versions. See GD Collector 30.000 Release Notes for more information.
- RELEASED EA Collector 30.100 on 20 April 2021. This version adds support for Kubernetes Events and Windows Events Logs collection for LM Logs, new OpenMetrics collection, and more. See EA Collector 30.100 Release Notes for more information.
- ADDED support for all identifiable transmission protocols (beyond TCP and UDP) supported by Netflow and IPFIX.
- FIXED an issue where some sensitive information (such as passwords and API keys) is masked during configuration but not in responses.
- DEPRECATED the Safe LogicModule Merge (SLM) feature in LM Exchange. SLM will be removed in v.155. This removal is temporary as we continue to update the LM Exchange UI and capabilities, and we plan to reintroduce the functionality in a future release.
- RELEASED v1.1.0 update for our official Ansible integration. This release includes support for enhanced provisioning functionality and support for auto-balanced collector groups. The certified integration is available now at Automation Hub, and the community version is still available via Ansible Galaxy. See the documentation for the Ansible Integration.
- FIXED an issue where exporting existing HTTP integration would return a 500 error code when the payload format is null or empty. The payload is expected to be one of the following: form data, JSON, plain text, url-encoded form data, or XML. As long as the payload is valid, the integration should export to a JSON file.
- ADDED filters for logs messages based on alert severity (Critical, Error, Warning). The clickable icons are located next to the Raw Logs icon. There will also be an icon on the log messages that generated an alert.
- ADDED a new method for deploying the LM Logs Azure integration. This deployment option streamlines the creation of the Azure Function and Event Hub with a button click, and also provides an easier method for forwarding logs to these new resources. You may find this useful if you are unfamiliar with Terraform or Gradle, which were previously the only deployment options offered.
- FIXED an issue where logs failed to initially load if a user did not have access to all devices and the user would need to select a resource group to see the logs they had access to. This issue has been corrected and logs for all devices a user has access to will be displayed without action required.
- KNOWN ISSUE If you delete an alert condition from a log processing pipeline in LM Logs, the pipeline will not match.
- CHANGED the requirements for Two Factor Authentication to make phone numbers auto-populated and not editable by the user. A notification message will display to 2FA users that they will need to update their phone numbers beginning in the next release.
- FIXED an issue with SSO that prevented users from signing in to all portals if they used the same IDP provider (such as Azure) for multiple portals.
- FIXED an issue where expressions containing parentheses in AppliesTo criteria returned an invalid expression error. This was caused by a check for sensitive properties and has been reverted.
- FIXED issues where some LogicModule datapoints would lose metric names upon import from repository.
- FIXED issues where Interface names did not appear in Graphs and Reports if they contained double quotes.
- FIXED the sorting behavior of Resource Metric Trends Report.
- CHANGED the workflow of system.hoststatus property to improve updates for the status of devices (normal, dead, dead-collector).
- FIXED issues where properties that are case insensitive were treated as different properties at different levels. With the exception of system properties, properties are now case insensitive across levels, and if the child property is a different case it will override the parent property. In appliesTo functions, the device will match from the immediate child value of the property.
- FIXED an issue that caused instance-level properties to be overridden in some cases.
- ADDED a note to the Python SDK documentation. For Python SDKs, the REQUEST parameters can contain camelCase or an underscore. However, the RESPONSE parameters will always contain an underscore. See LogicMonitor SDKs.
- FIXED an issue where the getAlerts endpoint was returning “No Data”. See “Sunset of the RPC API”.
- FIXED an issue where users were not seeing options to “Add dashboard” and “Add dashboard group” when they were assigned the Manage permissions.
- CHANGED how hashcodes are calculated to improve performance and reduce the gaps displayed in the Website’s graph.
- CHANGED the column length of Website folder names to support up to 255 characters (similar to resource group names).
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 the General Updates section.
|Microsoft_Azure_SignalR||(DataSource) Measures the number of connections, amount of traffic and the percentage of system and user errors for Azure SignalR.|
|(1 DataSource, 1 PropertySource) Monitors physical memory metrics. Excludes remaining datapoints present in NetSNMP_Memory_Usage due to Solaris not returning data or consistently reporting 0 values for those metrics.
See NetSNMP_Memory_Usage in Updated LogicModules.
|(2 PropertySources) Added SuperMicro specific ERI to ensure that IPMI servers are properly merged with their corresponding ESXi instances. Fixed conditional logic in addERI_ESXi for block that was not supposed to execute against UCS devices.|
|(6 DataSources) Add hardcoded SNMP timeout to scripts since default timeout was too short for successful ad/collection for some devices.|
|AWS_RDS||(DataSource) Fix graphs. Revert accidental inclusion of timezone in all day alert timeframe.|
|(4 DataSources) Changed collection interval to 1 minute. Previous interval of 2 minutes was populating invalid data. Please note that this change may result in increased Cloudwatch costs due to more frequent polling.|
|BGP_Topology||(TopologySource) Added previously undeclared variable for toggling debug output.|
|Cisco_CUCM_CollectionPath||(PropertySource) Ensure that the correct path separator for the Collector OS is used in the set property.|
|CiscoSLA_jitter-||(DataSource) Remove alert threshold from MOS datapoint. Moved alerting to MOSAlerts complex datapoint which ignores 0 scores, which indicate that MOS data was not generated. Added second complex datapoint, MOSDataNotGenratedAlerts, to optionally alert on 0 scores, note that the alert threshold is not set by default.|
|(12 DataSources, 1 PropertySource) Tracks throughput, latency, queue depth, caching, IOPs, status and health of network interfaces, volumes, disks, vdisks and pools . Also monitors jobs, storage allocation and controller performance. Provides health status for controllers, ports, PSUs, fans, drawers and enclosures.|
|LogicMonitor_Collector_CredentialVault||(DataSource) Replace VaultAPIResponseTime with a complex datapoint that returns accurate values.|
|Microsoft_Azure_ApplicationGateway_v2||(DataSource) Removed BlockedCount, BlockedRequestCount, CPUUtilization and MatchedCount datapoints which were not recognized as valid by the API.|
|Microsoft_Azure_Function||(DataSource) Added datapoints for average response time, raw response time, request count and HTTP 4xx response counts.|
|Microsoft_Azure_BlobStorage||(DataSource) Updated Transactions_raw datapoint to use the current Azure aggregation method and changed type from derive to gauge to show request counts instead of rate.|
|Microsoft_Azure_ExpressRouteCircuitPeering||(DataSource) The AZURE EXPRESS ROUTE CIRCUIT PEERING collection method now uses the Get Peering Stats API.
Due to the resulting change in returned data the state datapoint has been removed and datapoints for secondaryBytesIn and secondaryBytesOut have been added. The totalBytes complex datapoint expression has been updated to include the two new datapoints.
As a result, the primaryBytesIn and primaryBytesOut datapoints now return data, but the state datapoint no longer does.
|(2 ConfigSources) Fixed grouping.|
|(24 DataSources, 2 PropertySources) Removed extraneous try/catch statements which were obscuring errors.|
|Netflow_Device_Heartbeat||(DataSource) Updated netflowHeartbeat and netflowAgentId datapoints to use the corresponding newly added radio buttons.|
|NetSNMP_Memory_Usage||(DataSource) Updated AppliesTo to exclude Solaris devices. Please use the new modules mentioned above to monitor Solaris memory usage.|
|Oracle_Database_RMANAllBackupFilesSets||(DataSource) Stop printing the hardcoded SQL query as part of active discovery and collection output.|
|PaloAlto_FW_DroppedPackets||(DataSource) Updated collection script to use Long values to prevent integer overflows.|
|SNMP_Network_Interfaces||(DataSource) Added filters for common unwanted interfaces that were being filtered in snmp64_if-. Do not delete inactive instances. Ensure module works on all supported collector versions. Moved InTotalPkts and OutTotalPkts calculation to collect script. Alerting added for InDiscardPercent, OutDiscardPercent, Status and StatusFlap .Implemented “interface.description.alert_enable” ILP functionality for enabling alerting only on interfaces / instances that meet the regex criteria. Only set the description property when a description was set by the user, otherwise set to the interface ID and MAC address of the interface. Check both 32 and 64 bit OIDs for data. Added legacy “ActualSpeed” and “ActualSpeedUpstream” properties alongside newer “in_speed” and “out_speed” (ActualSpeed and ActualSpeedUpstream are meant to be given in Mbps, while in_speed and out_speed are meant to be giving in bps.). Performed sanitation on the interface descriptions. General code cleanup.
Adjust the Status datapoint to separate Alerting Off from Administratively Down, shows -1 for “Alerting Off” and 0 for “Administratively Down”, previously reported 0 for either state.Interfaces are now discovered during AD even if the interface only reports traffic on InOctets or OutOctets. Added AdminState, OutTotalPkts and InTotalPkts datapoints. Updated technical notes. Updated complex datapoints expressions for InDiscardPercent and OutDiscardPercent.
NOTE: snmp64_If- used the wildalias/description of an instance for filtering. While this is still true for SNMP_Network_Interfaces, the actual description equivalent is now in the ILP “auto.interface.alias”, so the code compares the regex in interface.description.alert_enable to the auto.interface.alias ILP. This was done to make sure that customers moving from snmp64_If- could use the same regex configuration. No changes are required as long as the interface.description.alert_enable ILP has been defined on a host level.
|VMware_ESXi_DatastorePerformance||(DataSource) Fix regression that removed discovery filter for virtual volumes. Note that this will result the deletion of discovered virtual volume instances.|
|VMware_ESXi_Resources||(DataSource) Updated display name.|
|VMware_Horizon_DesktopPools||(DataSource) Added datapoint for the provisioning status of a given desktop pool.|
This table lists LogicModules which we are deprecating in this release. This means that these LogicModules will be removed in a future release. A replacement LogicModule is listed, if there is one available.
|Details||End of Support Date|
|(DataSource) New module uses scripted active discovery to ensure that instance names are unique and nonephemeral.||2021-05-21|
For the list of LogicModules deprecated over the past five 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.
Distributed Tracing enters beta
LogicMonitor’s distributed tracing functionality will be entering beta soon! With this new distributed tracing capability, you will be able to forward traces from your instrumented applications to LogicMonitor. This will enable you to see end to end traces as they flow through the services in your environment (from a new Traces page in LogicMonitor), presented with contextual metrics and logs to enable faster troubleshooting and more proactive identification of performance bottlenecks.
To participate in this beta, fill out this form: Tracing Beta Survey
Push Metrics API enters beta in production environments
The Push Metrics API is now available for beta participants in production environments, but the feature must be enabled. Prior to enablement we would like to discuss best practices for testing and implementation as well as pricing considerations once the feature is generally available.
To participate in this beta, fill out this form: Push metrics API Production Beta
OpenMetrics DataSource Wizard enters beta
The OpenMetrics DataSource Wizard beta is available as an open beta in both sandbox and production environments. The wizard requires the EA Collector 30.100 or later. The wizard can be used to quickly load OpenMetrics (Prometheus exposition format) data from a provided URL endpoint and create a datasource for ingesting the data into your LM account.
To participate in this beta, fill out this form: OpenMetrics Beta Survey
Sunset of the RPC API
We have decided to focus on improving the LogicMonitor Rest API, which has higher security standards and integration capabilities that are more in-line with our future development goals. This means that we are preparing to end support for the RPC API with the upcoming release of LogicMonitor v.156.
If you are using the RPC API for Ansible, reach out to Support for guidance on migrating playbooks to the REST API.