Platform Release Notes Timeline

v.146 Release

IMPORTANT: Beginning with the rollout of v.146, LogicMonitor is updating its new version deployment window to 7:30-10:30 p.m. PT (previously, the window was 6-9 p.m PT). We will continue to provide in-app notification 48 hours in advance of a new version deployment.

General Enhancements and Fixes

Alerting

• Ability to link alert to its associated components. The alert detail pane now provides hyperlinks to the resource/website/service associated with the alert and the DataSource (if applicable).
• (FIX) Alert acknowledgement. Resolved an issue that was causing exceptions when users with a particular combination of permissions attempted to acknowledge alerts.
• (FIX) Cleared ConfigSource alerts. Fixed issue preventing cleared alerts triggered by ConfigSources from displaying in the Alerts page.
• (FIX) Time zones in graph legends. Resolved issue where graph legends (as displayed on the Graphs tab of the alert detail pane) were not honoring the user’s configured time zone.
• (FIX) Severity icon display. Resolved an issue preventing the display of severity icons in some cases when viewing the pop-out version of an alert from the Alerts page.

Cloud Monitoring

• AWS updates:
  • AWS Bahrain region added. Added support for the AWS Bahrain region (me-south-1), which is the first AWS region in the Middle East. Customers can now monitor services in the Bahrain region that are supported by LogicMonitor’s AWS monitoring.
  • New StorageType property for AWS RDS. Added StorageType as a property for AWS Relational Database Service (RDS). This new property (system.aws.storageType) allows logical grouping and filtering according to StorageType.
  • (FIX) AWS Kinesis Streams permissions. Previously, AWS Kinesis Streams permissions were not being properly tested. In some cases, this resulted in customers not being alerted that additional permissions were required to be able to monitor AWS Kinesis Streams from the LogicMonitor portal. This issue has been resolved.

Dashboards

• Alert List widget. The behavior of the anomaly filter available in the alert list widget configurations now aligns with that of the anomaly filter available on the Alerts page.
• (FIX) Custom Graph widget. The Custom Graph widget was returning an “invalid virtual datapoint expression” error when attempting to calculate virtual datapoints that referenced datapoints belonging to the same DataSource, but applying to different resources. This issue has been resolved. If you previously experienced this issue, open the Custom Graph widget configuration dialog and simply save the current configurations – no edits are necessary.
• (FIX) Rounding of Y-axis values. In some cases, the Y-axis value for some graphs was not displaying as a rounded value. This issue has largely been resolved, although there is still a remaining corner case that we are actively working on where non-rounded values still display if display type is selected as “Line” and data is constant (data is displayed in a straight line) for virtual datapoints

Kubernetes Monitoring

The following new features and improvements will be available with the new v5.0.0 version of Argus, which is targeted for arrival in early January.

• Avoiding name conflicts in discovery. To avoid name conflicts and subsequent issues with discovery, the following enhancements were made:
  • Resource type (for example, “Pod”) is appended by default to the LogicMontior display name
  • New Argus Helm chart options, FullDisplayNameIncludeNamespace and FullDisplayNameIncludeClusterName, are available to append namespace and cluster name respectively to the LogicMonitor display name (default: false). You may find that enabling one of these two new options is useful for avoiding naming conflicts in cases where pods with the same names are running across multiple namespaces and/or clusters.
  • For resources that fail to be added due to name conflicts, the conflicting resource will be added to a dynamic group named “_conflicts”.
• Discovery filtering by pod name. Pod name is now available for use with discovery filtering, including handling of special characters such as hyphens. You may find this useful for filtering pods in/out of monitoring based on names rather than labels.
• Discovering EKS Fargate nodes and pods. Previously, nodes and pods for EKS Fargate weren’t being discovered properly due to shared IPs, but no host network specification in the pod manifests (EKS Fargate pods each run on a distinct node and share IPs, but don’t use the Kubernetes Host Network specification). To account for this, we’re now categorizing pods with the EKS Fargate label “eks.amazonaws.com/fargate-profile” as pods configured with host networking. This will ensure (1) the right value for the system.hostname property gets set, (2) the right DataSources apply, and, most importantly, (3) there are no discovery conflicts between pods and nodes for EKS Fargate.

LM Exchange

• New LogicModule statuses. LogicModule statuses “Beta” and “Deprecated” now display in the LogicModule metadata table.

LM Logs

• Log events +/- three hours no longer accepted. Log events with timestamps more than three hours in the past or future are no longer accepted, and will result in a new 4006 API response code. This is to ensure relevance of data and protect against misconfigured timestamp settings.

Network Traffic Flow Monitoring

• New benchmarks. New capacity benchmarks for network traffic flow have been published for the Large, XL, and XXL Collectors. These benchmarks show a dramatic increase in the number of flows per second that can be comfortably monitored and were reached as a result of an ongoing initiative to enhance and optimize LogicMonitor’s network traffic flow monitoring capabilities. See Collector Capacity for the new benchmarks.
• Support for sFlow version 5. Added support for sFlow version 5 (Collector version 29.105 or higher is required).
• DNS lookups. Increased the DNS cache storage duration to 24 hours (previously duration was 30 minutes) to resolve repeated DNS queries preventing the resolved names from displaying.
• (FIX) IPv6 address format display. Normalized IPv6 address format display for NetFlow IPv6 endpoints that do not resolve via DNS.

REST API

• (FIX) Locked API tokens. Previously, locked API tokens due to multiple unsuccessful authentication attempts were causing an exception to occur. This issue has been resolved.
• (FIX) Updating a device via PATCH request. Previously, submitting a PATCH request to modify both a device “name” and its customProperties would result in the device name updating to the name of one of the customProperties. This issue has been resolved.
• (FIX) /apiStats/externalApis. Previously, /apiStats/externalApis was returning separate values for API calls to the same endpoint depending on whether the user made the call with or without a trailing forward slash (/). This has been corrected and calls with either variation are now appropriately identified and aggregated as a single entry in the response.

Website Monitoring

• New Web Check properties. Several new properties are now available for manipulating the settings of Web Checks. Specifically, these settings provide some flexibility in cases where sites may load slower than the default timeouts used by LogicMonitor’s external checkpoints.

  The following built-in properties all default to 30 seconds and all support an acceptable value range between >0 and <=60.

  • website.http.client.so.timeoutInSec (socket timeout in seconds)
  • website.http.client.connect.timeoutInSec (TCP connection timeout in seconds)
  • website.http.client.read.timeoutInSec (read timeout in seconds)

New, Updated, and Deprecated LogicModules

Recently released to the LogicMonitor public repository, our new and updated LogicModules are available for import to expand and enhance your monitoring coverage.

New LogicModules

Updated LogicModules

Deprecated LogicModules

LogicMonitor deprecates LogicModules for a variety of reasons. Most often, it is because we have published a replacement LogicModule that provides superior access to the monitored technology (for example, supports more versions of the technology or provides improved scalability).

However, there are times when a LogicModule is deprecated with no replacement (for example, when a technology becomes defunct or security issues beyond LogicMonitor’s control arise).

Note: When importing a replacement LogicModule, you will not experience any immediate data loss due to the name variation that LogicMonitor expressly adds. However, there will be a diversion in data collection between the deprecated and new LogicModule, and you will potentially collect duplicate data and receive duplicate alerts for as long as both LogicModules are active. For this reason, we recommend that you disable monitoring of the DataSource instances at the resource or resource group level after you have imported its replacement. When DataSource monitoring is disabled in this way, it stops querying the host and generating alerts, but maintains all historical data. At some point in time, you may want to delete the legacy DataSource altogether, but consider this move carefully as all historical data will be lost upon deletion. For more information on disabling DataSource monitoring, see Disabling Monitoring for a DataSource or Instance.

Entering Beta: Push Metrics API

LogicMonitor is developing a Push Metric API in order to allow metrics to be sent directly to LogicMonitor without the use of a Collector. Some technology landscapes where this capability is becoming vital include server-less infrastructures such as AWS Lambda, large distributed microservices environments with custom metrics (including business metrics), and IoT environments.

Beta for Push Metrics API is targeted for January. If you have a compelling use case and the resource availability, and would like to be considered for participation, please complete the Customer Beta survey.

v.145 Release

General Enhancements and Fixes

Alerting

• Bulk alert acknowledgement. The new UIv4.1 version of the Alerts page, rolled out in v.143, now supports the ability to acknowledge multiple alerts at once.
• Dynamic threshold usage limit. The usage limit calculation for dynamic thresholds has been updated to use the contracted resourced count rather than the current resource count. The new calculation (contracted resource count * 8) more accurately (and consistently) reflects dynamic threshold usage limits.
• (FIX) Alert overview graphs. Customers without access to the dynamic thresholds feature were receiving permissions errors when attempting to view the overview graph that displays as part of the Overview tab of an alert’s detail view (found on the Alerts page). To resolve this issue, overview graphs will no longer attempt to load expected ranges in portals where dynamic thresholds are not supported.
• (FIX) Detail URL for cleared alerts. When opening the detail views for cleared alerts in new browser tabs—either from the LogicMonitor interface or from delivered alert notifications that incorporate the ##ALERTDETAILURL## token—the resulting web pages were opening as blank pages. This has been fixed.

Cloud Monitoring

• AWS updates:
  • AWS Africa region added. Added support for the AWS Africa region (af-south-1), which is the first AWS region in Africa. Customers can now monitor services in the AWS Africa region that are supported by LogicMonitor’s AWS monitoring.
  • Updated AWS Direct Connect connection state mapping. AWS Direct Connect is changing from a “default to unavailable” to a “default to available” for monitoring. There remain two connection states for removing instances (“Deleting” and “Deleted”) and three connection states that are unavailable for monitoring (“Requesting”, “Ordering” and “Rejected”). Remaining connection states will map to an available state, allowing clients to monitor in LogicMonitor.
  • Using recommended AWS STS methods. LogicMonitor has updated the method it uses to obtain cross-account authorization tokens from AWS Security Token Service (STS). The new method follows AWS’ best practices and will allow for easier future addition of new AWS regions to the LogicMonitor portal. No action is required on the customer’s end.
  • (FIX) AWS Trusted Advisor API. As a result of changes made to the AWS Trusted Advisor API, several DataSources were not associating: AWS_IAM_ServiceLimits, AWS_VPC_TrustedAdvisorServiceLimit, and AWS_EC2_TrustedAdvisorServiceLimits. To resolve this issue, LogicMonitor has updated the method for validating and calling the Trusted Advisor API.
• Azure updates:
  • Name adjustments for Notification Hubs and SQL Elastic Pools services. Previously, when attempting to change the display names of Notification Hubs and SQL Elastic Pools services with forward slashes (/) in their resource names, errors were returned. To resolve this issue, forward slashes found in the names of Notification Hubs and SQL Elastic Pools services will be replaced with colons (:). Note: Only resource names are affected by these changes; forward slashes may still appear in display names, where permitted.
  • (FIX) Billing data calculations. There was an issue in calling cached RateCards to calculate the Azure billing data. This is fixed and should require no action from the clients.

Collectors

• EA 29.104. Collector version EA 29.104 was released on November 10. Collector releases are deployed independently of LogicMonitor platform releases. For more information on the various Collector versions available for upgrade and the differences between EA (early access), GD (general deployment), and MGD (minimum general deployment) versions, see Collector Versions.

Dashboards

• (FIX) NOC widget. Instance-level filters containing OR operations, as formatted with the pipe symbol (|), were not being correctly evaluated, causing a “Resource Not Found” error to be returned by the widget display. This has been fixed.

LM Exchange

• (FIX) LM Locator code display. The LM Locator code was not displaying for installed LogicModules. Impacting the Exchange and Settings pages, this has been fixed.

Network Traffic Flow Monitoring

• (FIX) NBAR2 application type. Application type (as sourced from NBAR2) was not displaying properly in the Traffic Tab visualizations for network traffic flow data. This has been fixed.

Role-Based Access Control

• Improved error handling when acknowledge privileges are missing. More descriptive error messages are now returned when users with SDT-only or threshold-only privileges for a resource attempt to acknowledge alerts triggered by that resource.

New, Updated, and Deprecated LogicModules

Recently released to the LogicMonitor public repository, our new and updated LogicModules are available for import to expand and enhance your monitoring coverage.

New LogicModules

Updated LogicModules

Deprecated LogicModules

LogicMonitor deprecates LogicModules for a variety of reasons. Most often, it is because we have published a replacement LogicModule that provides superior access to the monitored technology (for example, supports more versions of the technology or provides improved scalability).

However, there are times when a LogicModule is deprecated with no replacement (for example, when a technology becomes defunct or security issues beyond LogicMonitor’s control arise).

Note: When importing a replacement LogicModule, you will not experience any immediate data loss due to the name variation that LogicMonitor expressly adds. However, there will be a diversion in data collection between the deprecated and new LogicModule, and you will potentially collect duplicate data and receive duplicate alerts for as long as both LogicModules are active. For this reason, we recommend that you disable monitoring of the DataSource instances at the resource or resource group level after you have imported its replacement. When DataSource monitoring is disabled in this way, it stops querying the host and generating alerts, but maintains all historical data. At some point in time, you may want to delete the legacy DataSource altogether, but consider this move carefully as all historical data will be lost upon deletion. For more information on disabling DataSource monitoring, see Disabling Monitoring for a DataSource or Instance.

Entering Beta: Push Metrics API

LogicMonitor is developing a Push Metric API in order to allow metrics to be sent directly to LogicMonitor without the use of a Collector. Some technology landscapes where this capability is becoming vital include server-less infrastructures such as AWS Lambda, large distributed microservices environments with custom metrics (including business metrics), and IoT environments.

Beta for Push Metrics API is targeted for January. If you have a compelling use case and the resource availability, and would like to be considered for participation, please complete the Customer Beta survey.

v.144 Release

Feature Highlight: LM Logs

Launching on November 18, LM Logs offers a unique and unified approach to log analysis centered on algorithmic root-cause analysis. LM Logs analyzes log events after they are ingested and mapped to a monitored resource to identify normal patterns and deviations from these patterns: anomalies.

Log anomalies represent log events that are new, or seen for the first time on the monitored resource it’s associated with. These anomalies are displayed in two places: (1) the new Logs page, where you can review raw logs and investigate log anomalies across your entire infrastructure and (2) the Graphs tab for alerts, where they are displayed contextually with metric alerts to help speed troubleshooting.

To get logs into LogicMonitor, you can choose from one of our provided integrations or send custom logs directly to the logs ingestion API. For more information, see the LM Logs Documentation.

Platform Enhancements

Audit Logs

• (FIX) Capturing dynamic threshold updates. In some instances, updates to dynamic thresholds were not being captured comprehensively in the audit logs. This has been corrected.

Cloud Monitoring

• AWS updates:
  • AWS SWF Workflow support for duplicate names. Domain names will now be included as part of SWF Workflow naming conventions to support the presence of identical names across multiple domains. Note: Any dashboards that have been customized with AppliesTo statements that reference specific SWF Workflow names may need to be updated to accommodate this new naming convention.
  • (FIX) AWS Kinesis Stream purging. Some removed AWS Kinesis Streams were not being properly purged from the portal. A fix has been made to resolve this issue moving forward and to retroactively remove any streams that were falsely persisting.
  • (FIX) Route53 instances. Two issues pertaining to Route53 instances have been resolved:
    • Custom AWS tags were not properly coming through on Route53 instances.
    • Pagination was limited to 100 instances, even if more instances were present.
• GCP updates:
  • (FIX) GCP usage count. An issue was causing inconsistent display of GCP usage from the resource usage count tables available on the Account Information page (Settings | Account Information). This has been fixed.

Kubernetes Monitoring

• (FIX) Data collection for host-networking pod configurations. The system.ips property wasn’t being populated properly for some pods configured with host-networking, which caused Ping and Host Status data collection issues for these pods. This has been fixed.

LM Exchange

• (FIX) Importing modules. When importing a module from the public repository, an issue was causing the install status to display “Installing…” indefinitely. This has been fixed.

Network Traffic Flow Monitoring

• Exclude conversations filter. The conversations filter on the Traffic tab has been enhanced to support the exclusion of explicit conversations between one-to-one, one-to-many, many-to-one, or many-to-many endpoints.

User Interface (UI)

• (FIX) Visual display errors for graphs on Alerts page. For graphs that compare usage to total capacity, the visual display was incorrectly stacking, causing visual misalignment with actual capacity values. This was happening for graphs that displayed on the Alerts page; graphs that displayed on the Resources page did not experience this issue. This issue has been fixed.

New, Updated, and Deprecated LogicModules

Recently released to the LogicMonitor public repository, our new and updated LogicModules are available for import to expand and enhance your monitoring coverage.

New LogicModules

Updated LogicModules

Deprecated LogicModules

LogicMonitor deprecates LogicModules for a variety of reasons. Most often, it is because we have published a replacement LogicModule that provides superior access to the monitored technology (for example, supports more versions of the technology or provides improved scalability).

However, there are times when a LogicModule is deprecated with no replacement (for example, when a technology becomes defunct or security issues beyond LogicMonitor’s control arise).

Note: When importing a replacement LogicModule, you will not experience any immediate data loss due to the name variation that LogicMonitor expressly adds. However, there will be a diversion in data collection between the deprecated and new LogicModule, and you will potentially collect duplicate data and receive duplicate alerts for as long as both LogicModules are active. For this reason, we recommend that you disable (rather than delete) the deprecated LogicModule after you have imported its replacement to provide time to (1) verify that it is working as expected and (2) build up a new set of historical data.

Entering Beta: Push Metrics API

LogicMonitor is developing a Push Metric API in order to allow metrics to be sent directly to LogicMonitor without the use of a Collector. Some technology landscapes where this capability is becoming vital include server-less infrastructures such as AWS Lambda, large distributed microservices environments with custom metrics (including business metrics), and IoT environments.

Beta for Push Metrics API is targeted for December. If you have a compelling use case and the resource availability, and would like to be considered for participation, please complete the Customer Beta survey.

v.143 Release

Feature Highlights

Feature Highlight: Alerts Page Refresh

LogicMonitor is releasing significant UI enhancements for the Alerts page. The new UI is more intuitive and efficient, featuring:

• Increased data density
• Fewer clicks to accomplish a task
• Faster loading times

While the capabilities of the new Alerts page UI are largely parallel to those of the previous UI, some new functionality is being introduced, including:

• Bulk SDT action enhancements. You can now put parent devices (or device groups) into SDT from the bulk SDT action.
• Ability to escalate alerts or add notes to alerts as bulk actions. You can now escalate multiple alerts or add a note to multiple alerts at once from the bulk actions menu.

  

• Inverse alert selection. When selecting multiple alerts for the purpose of performing an action in bulk, the selection dropdown offers the ability to invert current selection, allowing you to select all except those currently selected.
• User-friendly alert detail display. The Overview tab features several new user-friendly display features that make alert detail viewing more efficient and intuitive.

  

Note: Upon deployment of the new UI, the left-hand Alerts navigation menu will automatically open the new Alerts page. However, you can still access the prior version of the Alerts page by removing the “s” from the very end of the Alerts page URL (transforming “/alerts” to “/alert”). The prior version of the Alerts page will remain available through at least version v.144.

For more information on using the new UI, see Managing Alerts from the Alerts Page.

Feature Highlight: New Profile Menu

The left-hand navigation menu features a new Profile menu. Only available when viewing areas of the product with version 4.x of the UI (currently the Alerts and Exchange pages), this menu is unique per user, allowing you to manage your user account, access support/training, configure various appearance settings, and log out.

Note: When viewing areas of the product with version 3 of the UI, you can find these options (manage user account, access support/training, log out) in the upper right corner of the platform header.

Platform Enhancements

Alerting

• Alert notification suppression independently configurable from alert generation. Alert notification suppression is now independently configurable from the alert generation capabilities of dynamic thresholds. This means you can have dynamic thresholds that trigger alerts for anomalies, suppress notifications for alerts that correspond to expected performance, or both. This is useful when there are different use cases for suppression and alert generation (for example, a percentage-based metric for which there is a very clear good and bad range may benefit more from suppression than alert generation). For more information on using these capabilities independently or in cooperation, see Enabling Dynamic Thresholds for Datapoints.

  

Alert Integrations

• Improved alert clear behavior around instance deletion. Several enhancements have been made in this area to prevent orphaned tickets in third-party integrations:
  • If an alert is cleared and the instance triggering the alert then gets deleted via Active Discovery, the alert will be cleared prior to the instance being deleted.
  • If an alert’s severity level is upgraded and, prior to sending notification of upgrade, the instance triggering the alert is deleted via Active Discovery, an alert clear will now be sent for the initial severity level. Previously, this notification was unintentionally suppressed due to alert upgrade.
  • If an alert’s severity level is upgraded and, prior to sending notification of upgrade, the upgraded alert is cleared and the instance triggering the alert is then deleted via Active Discovery, an alert clear will now be sent for the initial severity level. Previously, this notification was unintentionally suppressed due to alert upgrade.
• (FIX) ConnectWise alert integration cloning. Resolved an issue that was preventing the cloning of ConnectWise alert integrations without “Escalated” payloads. This has been fixed and the ability to clone a ConnectWise integration is now available regardless of the types of payloads configured for it.

Dashboards

• (FIX) NOC widget. Fixed an issue introduced by an update to the Chrome browser that was displaying hyperlinks in the NOC widget for non-privileged users (users with read only permissions for dashboard). The hyperlinks were leading non-privileged users to invalid URLs. This has been fixed and non-privileged users will no longer see rendered hyperlinks in the NOC widget.

Devices

• (FIX) Device association with DataSources and dynamic groups. Resolved an issue that was preventing DataSources and dynamic groups from applying to a device (despite the device matching the AppliesTo statement of DataSource(s) or dynamic group(s)) after the device’s properties were updated by an ERISource PropertySource. While this issue is resolved and will not occur moving forward, remedial steps must be performed on any impacted devices and/or dynamic groups in order to enable appropriate associations:
  • To manually fix missing DataSource associations… Open each device in the Resources page and select Manage | Force DataSource Re-Match.
  • To manually fix missing dynamic group associations… This can be accomplished using one of the following two methods:
    • Temporarily update AppliesTo statement for dynamic group. Temporarily update the AppliesTo statement for each dynamic group in order to trigger dynamic group evaluation across all devices. It is recommended that you add an OR condition that adds a dummy property to the AppliesTo statement so as not to remove any currently associated devices or associate any new devices. To accomplish this, put the existing statement in parentheses and then append the OR condition. For example: (<existing AppliesTo statement>) || dummy.property == xyz.

      After saving the new statement and waiting a few moments, revert the AppliesTo back to its original statement and save once again.

    • Create a temporary PropertySource. Create and trigger a PropertySource that sets a dummy property on the devices whose memberships need to be reevaluated. The PropertySource can consist of a script as simple as a one line print statement: println("auto.triggerdynamicgroups=true"). To trigger immediate evaluation of the PropertySource across your devices, select More | Run PropertySource from the PropertySource definition. Once the dynamic groups are updated, delete the PropertySource.
• Helper text added to Dynamic Group configuration window. The following informational note has been added to the Add Dynamic Group and Update Dynamic Group configuration windows to provide further explanation of which properties the group’s AppliesTo statement evaluates.

  “Note: To avoid circular references, the criteria that determines which devices are auto-assigned to a dynamic group (i.e. the AppliesTo script) can only evaluate properties of the host itself, not any inherited properties from those groups of which it is a member.”

• Improved warning message when adding devices to a device group. When adding devices to a device group, if a Collector (or Auto-Balanced Collector Group) other than the one currently assigned to the device is chosen, the following warning now displays in the UI.

  “The highlighted devices are not being monitored by their preferred collector/group. To change the preferred collector or to perform failback, go to Collector Settings. In case of a device being monitored by an ABCG, check if the device has been moved to other group.”

Kubernetes Monitoring

• Editable and downloadable YAML configuration files. The Add Kubernetes Cluster wizard now provides editable and downloadable YAML configuration files for the LM Container Argus and Collectorset-Controller deployments. You may find this install process simpler than the previous copy/paste Helm commands (the new process is a one-line install using the Kubernetes cli to apply from the YAML file), and particularly useful when customizing configuration options that weren’t exposed in the UI wizard previously (all options are present in the YAML file).
• Kubernetes and Helm version properties. New properties are automatically added at the cluster (group) level to capture Kubernetes and Helm versions. This information is intended to help provide the LogicMonitor team the information they need in troubleshooting situations.
• Disabling Spinnaker versioning. New Helm chart options have been added to disable Spinnaker versioning. If you use Spinnaker, you may find this useful for avoiding issues with Spinnaker versioning on the config maps/secrets.
• Resource deletion retry. Argus will now retry deleting resources (e.g. pods) in monitoring when the initial delete request fails. This compensates for any issues that may interfere with initial deletion, helping to ensure monitoring stays up to date.
• (FIX) Improved handling of duplicate resource names. Kubernetes resources with the same names in different namespaces of the same cluster were previously not properly added into monitoring. To resolve this issue, namespaces are now appended to resource names in this scenario to ensure unique naming.
• Argus version 4.2.0. In Argus version 4.2.0, which was recently released, pod naming convention changes from <pod name> to <pod name-namespace>. This change was made to accommodate pods with the same names running in different namespaces, but it will result in pods being deleted and re-added under the new naming convention. If you wish to avoid this, you can update your Argus image tag in Helm to 4.1.0 so that you do not get the 4.2.0 release. In a future release we will change this behavior so that pods can simply be renamed without being deleted/re-added.

Network Traffic Flow Monitoring

• Network traffic flow monitoring available for more systems. Adjusted flexibility of mandatory field requirements in traffic flows to allow for network traffic flow monitoring on systems that do not provide both source and destination ports and/or interfaces. Although dependent on specific models, this enhancement should serve to expand LogicMonitor’s network traffic flow monitoring support to Cisco ASA, Cisco Meraki, and VMware VeloCloud systems—as well as other systems not yet directly known to us.
• Support for the SNMP_Network_Interfaces DataSource. Interface descriptions can now also be obtained via the newer SNMP_Network_Interfaces DataSource. Previously, only the snmp64_if DataSource was supported for this purpose.
• Group-level filtering. The Traffic tab that displays at the device group level now offers the same filtering capabilities as the Traffic tab that displays at the device level.
• (FIX) NetFlow Device Metric report. Adjusted report to handle aggregate devices.
• (FIX) NetFlow Device Metric report. Resolved issue that was preventing report generation if fields were missing data.
• (FIX) Missing IFout field. Fixed issue causing the interface out ID to display as 2147483648 when IFout field was not found.

User Interface (UI)

• Continued expansion of usage summary counts. In v.141, LogicMonitor introduced several new usage count summaries on the Account Information page (Settings | Account Information) including usage counts for user roles, alert rules, dashboards, and others. Continuing with this initiative of enhanced tracking of resource usage, new usage counts have been added for session users, external API users, open alerts, and previous day alerts. In addition, these counts have been broken down into four logical grouping tables. For detailed descriptions of the various usage accounts available, see About the Account Information Page.
• Remote support status icon. The left-hand navigation menu features a new remote support status icon. This icon only displays if you are currently viewing an area of the product with version 4.x of the UI (currently the Alerts and Exchange pages). As discussed in Users, this icon provides the current status of LogicMonitor remote support access.

  

  Note: When viewing areas of the product with version 3 of the UI, remote support status displays in the upper right of the platform header.

New, Updated, and Deprecated LogicModules

Recently released to the LogicMonitor public repository, our new and updated LogicModules are available for import to expand and enhance your monitoring coverage.

New LogicModules

• AWS Elemental MediaConvert – 1 DataSource

  Monitors AWS Elemental MediaConvert job output duration, errors, and transcoding/standby time.

• Cisco_AIPSSM_Processor – 1 DataSource

  Replacing the SNMP-based Cisco AIP SSM Memory Pools DataSource, this new DataSource offers a scripted SNMP version that returns accurate values. If you were previously using the now-deprecated DataSource, it can be deleted as it was providing invalid data.

• Cisco ASA – 1 SNMP SysOID Map

  The \.1\.3\.6\.1\.4\.1\.9\.1\.2406 SNMP SysOID Map applies Cisco_ASA_* LogicModules to Firepower 2130 devices.

• Cohesity – 12 DataSources, 1 EventSource, 1 PropertySource

  Monitors metrics related to storage, clusters, nodes, consumers, hardware, and data protection for your Cohesity platform. For setup and monitoring details, see Cohesity DataProtect and DataPlatform Monitoring.

• VMware VeloCloud – 5 DataSources, 1 PropertySource

  Gathers metrics for VeloCloud edge health, throughput, performance, and errors via the VeloCloud Orchestrator API. Also gathers system CPU and memory metrics via SNMP. For setup and monitoring details, see VMware VeloCloud Monitoring.

Updated LogicModules

• Cisco_Meraki_Licensing – 1 DataSource

  Updated to no longer fail to collect data on devices that have a license expiration date set to “N/A”.

• Citrix_Netscaler_AAA – 1 DataSource

  Updated the metric type of the CurICASessions datapoint from derive to gauge.

• HP MSA – 10 DataSources

  The scripted DataSources in the HPA monitoring suite have been updated to improve handling of leading 0s in the authentication hash.

• Infoblox_Appliance_DHCPv4Statistics – 1 DataSource

  Changed the metric types of all datapoints from counter to derive.

• Linux_SSH_Filesystems – 1 DataSource
  • Replaced invalid characters in wildvalues. Note: Upon import of this update, instances with invalid characters in their names will be deleted and replaced with new instances; however, impact should be minimal as the replaced instances would not have been successfully collecting data.
  • Updated Active Discovery to no longer discover loop devices as they are dynamically allocated and thus always report 100% utilization resulting in unnecessary alerts.
• Microsoft SQL Server – 2 PropertySources

  The Microsoft_SQLServer_SQLAuthConnections and Microsoft_SQLServer_Connections PropertySources now include the loginTimeout parameter in JDBC strings to resolve high CPU usage on Collector v29.003 caused by the PropertySource script not timing out correctly.

• NetApp – 2 PropertySources

  The addCategory_NetApp and addCategory_NetApp_ESeries PropertySources now assign the category of “NetApp” to the system.categories property from API-based PropertySources rather than relying only on sysOIDs.

• NetSNMPCPUwithCores – 1 DataSource

  Updated the appliesTo function to associate with F5 devices.

• Nimble_Array_Info – 1 DataSource

  A value of NoData (rather than -1) is now returned for metrics that are not returned by the array.

• PaloAlto_FW_ThreatAnalysis_Events – 1 EventSource

  This LogicModule now accepts the property paloalto.timezone which specifies a timezone offset in hours. If this property is not set, the offset defaults to UTC (0). Customers should check their devices to ensure that event timestamps from their devices are in UTC and set this new property accordingly.

• Printer Consumables- 1 DataSource

  Added graphs and complex datapoints for status codes that are sometimes included as a negative return value for the Level metric, which should prevent incorrect graphs and false alerts. Added missing descriptions.

• Slack Events – 1 EventSource

  Resolved issue that was causing outage updates to be displayed as duplicates of the same event.

• SNMP_Network_Interfaces – 1 DataSource

  Fixed incorrect calculation of In/OutUtilizationPercent datapoint values.

• Topology Mapping – 1 TopologySource

  General updates to LogicMonitor’s topology-mapping-specific LogicModules include:

  • Networking_L2_snmpSwitch TopologySource

    Discontinued matching OUI and LLDP edges on Brocade devices due to non-existent edges being generated.

  • addERI_Device PropertySource

    Added new OIDs for ERT discovery.

• VMware vCenter Server Appliance – 10 DataSources

  Updated all VMware VCSA DataSources to accept credentials via the vcsa.user/vcsa.pass properties. To ensure backwards compatibility, the DataSources will fallback to using esx.user/esx.pass if no VCSA-specific credentials are provided. Customers should migrate their VCSA-specific credentials to the new properties at their earliest convenience.

• WinSystemUptime – 1 DataSource

  Added an UptimeDays complex datapoint to represent system uptime in days. Added missing datapoint descriptions.

Deprecated LogicModules

LogicMonitor deprecates LogicModules for a variety of reasons. Most often, it is because we have published a replacement LogicModule that provides superior access to the monitored technology (for example, supports more versions of the technology or provides improved scalability).

However, there are times when a LogicModule is deprecated with no replacement (for example, when a technology becomes defunct or security issues beyond LogicMonitor’s control arise).

Note: When importing a replacement LogicModule, you will not experience any data loss due to the name variation that LogicMonitor expressly adds. However, you will potentially collect duplicate data and receive duplicate alerts for as long as both LogicModules are active. For this reason, we recommend that you disable the deprecated LogicModule after you have imported its replacement and verified that it is working as expected.

v.142 Release

Platform Enhancements

Alerts

• (FIX) Alert filtering. Entering multiple exclude criteria for the instance filter (e.g. !(InstanceNameA | InstanceNameB)) was resulting in no filter exclusions for the instance filter. This was impacting both the Alert List widget and the Alerts page. This has been fixed.

Alert Integrations

• PagerDuty. Collector down alerts are now supported for PagerDuty alert integrations by default. To achieve this, the source fields in LogicMonitor’s default payloads were changed from "source":"##HOST####WEBSITE##" to "source":"##HOST## ##WEBSITE## ##AGENTID## ##AGENT_DESCRIPTION##".

Audit Logs

• Audit log entry restructure. Audit log entry descriptions for all operations performed on devices, DataSources, and instances have been restructured so as to facilitate parsing of audit logs in a more efficient manner. A typical format of an audit log entry now includes action, type, and description as key-value pairs. Other key-value pairs are additionally present depending upon the operation.

  

Dashboards

• (FIX) Gauge widget. The Gauge widget was failing to generate data when “last calendar month” was selected as the value in the Peak time range configuration. This has been fixed.

LM Cloud

• AWS updates:
  • AWS EMR cluster state mapping. The mapping of EMR cluster states to the system.aws.monitoringstate property has been updated. Previously, the cluster states of STARTING, BOOTSTRAPPING, and WAITING were mapped to a value of “2” which indicates unavailable. With v.142, these states are now being mapped to a value of “1”, which indicates OK, to ensure monitoring is being properly performed on allocated resources.
• Microsoft Azure updates:
  • New properties discovered for Azure VM. Operating system name and version are now being discovered as instance properties for existing and new Azure VMs. You may find this additional detail helpful when filtering or grouping by properties.
  • (FIX) Azure Storage Service Limits Probe collection method. A recent Azure API upgrade caused the Azure Storage Service Limits Probe collection method to collect service limits per region and not per Azure subscription. As a result, DataSources using this collection method began alerting because expected data was not being returned. This has been fixed.
  • (FIX) Upgraded Azure API. The API used for Azure VMs was upgraded in order to resolve an issue in which properties were being dropped due to discovery timeouts.

LM Container

• LM Container Argus v4 now available. A new major version of LM Container is now available that provides improved compatibility with LogicMonitor API rate limits; support for pod priority class; and toleration specifications that are helpful for preventing Argus, Collectorset-Controller, and Collector pods from being scheduled on tainted nodes. Because of the extent of the updates in this major version, you will need to opt in to this upgrade. For upgrade details and instructions, see LM Container Argus v4 Release.
• Discovery filtering. Discovery filtering has been added to LogicMonitor’s Kubernetes monitoring capabilities. This discovery filtering, which is similar to what is available via LM Cloud, can be used to exclude certain resources (for example, QA or dev deployments) from monitoring based on labels. For larger clusters where API server resources are not scalable, discovery filtering can help you better manage API server load due to monitoring. Discovery filtering can be configured in the LogicMonitor UI (from the Add Kubernetes Cluster wizard) or directly in your Helm deployment.
• (FIX) Dynamic node group queries. Queries for dynamic node groups based on worker role weren’t properly including the correct nodes in some cases; this has been fixed.

LM Exchange

• (FIX) Automatically Delete Instance slider state. Fixed issue in LM Exchange in which the Automatically Delete Instance on/off slider was visually rendering the state opposite to the actual state.

Network Traffic Flow Monitoring

• Enhanced filtering at device group level. The filtering options available for filtering network traffic flow data at the device group level are now at functional parity with those available at the device level.

Topology Mapping

• Node filtering. Node filtering based on edge type has been added to topology maps that display from the Resources page (on the Maps tab).

New, Updated, and Deprecated LogicModules

Recently released to the LogicMonitor public repository, import our new and updated LogicModules to expand and enhance your monitoring coverage.

New LogicModules

• Arista Switch – 3 DataSources

  Three new DataSources have been released to replace the now-deprecated and more general Arista_Switch_Storage DataSource. The new DataSources (Arista_Switch_FlashStorage, Arista_Switch_Memory, and Arista_Switch_StorageUsage) filter out instances to allow for separate DataSource monitoring of memory, flash storage, and standard storage. Alerts have been added for Arista_Switch_StorageUsage.

• Fortinet FortiGate – 1 PropertySource, 2 TopologySources

  For improved FortiGate topology mapping operations, two new TopologySources (Fortinet_FortiGate_HA and Fortinet_FortiGate_SDWAN) for generating HA and SDWAN edges respectively have been created. In addition, one new PropertySource (addERI_Fortinet_FortiGate) to support ERI discovery for Layer 2, Layer 3, high availability and SDWAN ERIs has been added.

  Note: As discussed in the Updated LogicModules section, updates to two existing LogicModules are also available for improved FortiGate topology mapping.

• HPE Nimble – 1 PropertySource

  A new PropertySource named addCategory_NimbleSSH was added to the HPE Nimble monitoring suite. This PropertySource tests SSH access to Nimble devices and applies the “NimbleStorageSSH” category.

  As noted in the Updated LogicModules section, enhancements have additionally been made to several existing HPE Nimble LogicModules.

• VMware NSX – 6 DataSources, 2 PropertySource, 2 ConfigSources

  Collects metrics for NSX manager system resource utilization and component status; NSX controller resource utilization; uptime and node failover status; and edge service health and interface throughput. Monitors configs for NSX controllers and edge services. For setup and monitoring details, see VMware NSX Monitoring.

Updated LogicModules

• APC_Environment_Monitor_Humidity- – 1 DataSource

  Fixed unclear descriptions and alert messages on the humidity threshold breach datapoints.

• AWS_RDS_ServiceLimits – 1 DataSource

  Added missing metric names that were causing data collection to fail.

• Cisco_FRU_Power – 1 DataSource

  Removed three complex datapoints (operatingStatusAlert*) and moved their alerting to the OperatingStatus datapoint.

  Important: Any instance-level tuning or alert rule configurations currently referencing these three removed complex datapoints will need to be reconfigured to reference the OperatingStatus datapoint. Historical data for the OperatingStatus datapoint will not be impacted, but historical data will be lost for the three removed operatingStatusAlert* complex datapoints.

• Cisco_NXOS – 1 ConfigSource

  Removed log4j usage due to incompatibilities with the version of the library bundled with Collector versions 29.102 and higher; updated filters for the DifferenceTest config check.

• Citrix_Netscaler – 1 ConfigSource

  Removed log4j usage due to incompatibilities with the version of the library bundled with Collector versions 29.102 and higher.

• DataCore_Symphony_VirtualDisks – 1 DataSource

  Removed unused jackson-databind import to align with Collector versions 29.102 and higher.

• Dell EMC – 1 PropertySource

  For improved topology mapping operations, updated the addERI_Linux PropertySource to set “Switch” as external resource type for Dell EMC networking devices.

• Device_BasicInfo – 1 PropertySource

  Updated to use the actual hostname instead of its string representation to generate values for the auto.network.names property. This prevents invalid values from being set for the property due to DNS resolution issues.

• Fortinet FortiGate – 1 DataSource, 1 PropertySource

  For improved FortiGate topology mapping operations, updates have been made to the Fortinet_FortiGate_HighAvailabilityPeers DataSource and the addERI_Device PropertySource.

  Note: As discussed in the New LogicModules section, three new LogicModules have been released for improved FortiGate topology mapping.

• HPE_Network_Config – 1 ConfigSource

  Removed log4j usage due to incompatibilities with the version of the library bundled with Collector versions 29.102 and higher.

• HPE Nimble – 5 DataSources, 1 PropertySource

  Updated the AppliesTo statement to use new “NimbleStorageSSH” category set by the newly-released addCategory_NimbleSSH PropertySource for the following SSH-based LogicModules: Nimble_Array_Info, Nimble_HDD_Disks, Nimble_SSD_Disks, Nimble_Volume_Latency, and Nimble_Array_Properties (PropertySource).

• Linux SSH – 1 DataSource, 1 PropertySource

  Updated the regex in the Linux_SSH_Filesystems DataSource to handle output split on multiple lines; added debug mode.

  Updated the Linux_SSH_Info PropertySource to use the actual hostname instead of its string representation to generate values for the auto.network.names property. This prevents invalid values from being set for the property due to DNS resolution issues.

• LogicMonitor_Portal_Metrics – 1 DataSource

  Removed usages of the commons-codec library, to align with Collector versions 29.102 and higher.

• Microsoft_Azure_BlobStorage – 1 DataSource

  Due to changes to the Azure Service Insights API, the collection interval for this DataSource has been increased to one hour. The previous one-minute interval was resulting in data collection issues caused by too-frequent polls of the API.

• Microsoft_Azure_ExpressRouteCircuit – 1 DataSource

  Increased the data collection interval to five minutes to match Azure’s recently adjusted minimum allowed collection frequency. The previous one-minute interval was resulting in gaps in historical data.

• Office365_MSOnline_AccountLicense – 1 DataSource

  Updated to support Microsoft Office 365 licensing SKU updates (see Microsoft documentation for a current listing of SKUs); added datapoints and graphs to track the total units.

  Important: There may be some historical data loss upon import due to instances being deleted and replaced with instances corresponding to the updated SKUs.

• OSPF_Neighbors – 1 DataSource

  Changed the metric type of the neighborEvents datapoint from gauge to derive; added datapoint and graph for the retransmit queue length.

• Palo Alto Firewall – 1 DataSource, 1 ConfigSource

  Fixed misleading description and alert message for the swap_pct_used datapoint found in the PaloAlto_FW_SystemResources DataSource.

  Removed log4j usage from the PaloAlto_FW_CLIConfigs due to incompatibilities with the version of the library bundled with Collector versions 29.102 and higher.

• RabbitMQ Queue – 1 DataSource

  Updated wildvalue to exclude special characters in instance names.

  Important: This may result in historical data loss for existing instances with special characters in their names due to new instances being created with sanitized names.

• snmpIf- – 1 DataSource

  Added StatusAlert complex datapoint similar to the datapoint already present in the snmp64_If- DataSource. Alerting has not been moved to the new datapoint to prevent instance-level alert rule changes. Note: An improved interfaces DataSource is targeted for release in an upcoming version.

• Topology Mapping – 2 PropertySources, 3 TopologySources

  General updates to LogicMonitor’s topology-mapping-specific LogicModules include:

  • BGP_Topology TopologySource
    • Disabled BGP topology for Fortigate devices due to merging issues caused by the use of restricted and overlapping private IPs.
    • Includes the BGP peer address during edge discovery.
  • Networking_L2_snmpSwitch TopologySource.
    • Added support for shared namespaces, short OUIs (organizationally unique identifiers) for mapping some IBM devices, and OUIs for some Emulex and PCS equipment.
    • Made minor fix to account for devices that do not return 802.1Q bridge table entries over SNMP, as is the case for some HP Switches.
  • OSPF_Topology TopologySource
    • Disabled OSPF topology for Fortigate devices due to merging issues caused by the use of restricted and overlapping private IPs.
    • Included the OSPF neighbor id during edge discovery
  • addERI_BGP PropertySource
    • Disabled BGP topology for Fortigate devices due to merging issues caused by the use of restricted and overlapping private IPs.
  • addERI_OSPF PropertySource
    • Fixed external resource type for OSPF switches that were incorrectly classified as routers.
    • Disabled OSPF topology for Fortigate devices due to merging issues caused by the use of restricted and overlapping private IPs.
• Viptela_System_Memory – 1 DataSource

  Added new SystemStatusMemTotal_KB datapoint for total system memory; updated memoryUtilization complex datapoint to account for total memory, buffers and cache.

• VMware VCenter – 1 TopologySource

  Change: Added safe navigation to the VMware_vCenter_Topology TopologySource to resolve topology generation issues resulting from an unknown HA state.

• WinVolumeUsage- – 1 DataSource

  Updated the Capacity Detail graph to scale by bytes rather than gigabytes.

Deprecated LogicModules

LogicMonitor deprecates LogicModules for a variety of reasons. Most often, it is because we have published a replacement LogicModule that provides superior access to the monitored technology (for example, supports more versions of the technology or provides improved scalability).

However, there are times when a LogicModule is deprecated with no replacement (for example, when a technology becomes defunct or security issues beyond LogicMonitor’s control arise).

Note: When importing a replacement LogicModule, you will not experience any data loss due to the name variation that LogicMonitor expressly adds. However, you will potentially collect duplicate data and receive duplicate alerts for as long as both LogicModules are active. For this reason, we recommend that you disable the deprecated LogicModule after you have imported its replacement and verified that it is working as expected.

Entering Beta

LogicMonitor is currently beta testing significant UI enhancements for the Alerts page. The new UI is more intuitive and efficient, featuring:

• Increased data density
• Faster loading times
• More advanced filtering options

Any customer with a sandbox portal will be able to test drive these UI enhancements in their sandbox portal, targeted for roll out October 6 (subject to change). To access the new UI, open the Alerts page and add an “s” onto the very end of the URL (transforming “/alert” to “/alerts”).

Feedback on the new UI is welcome and can be submitted right through your portal, as outlined in Accessing Support Resources.