Come join our live training webinar every other Wednesday at 11am PST and hear LogicMonitor experts explain best practices and answer common questions. We understand these are uncertain times, and we are here to help!
Upon your account’s upgrade to v.135, import our new and updated LogicModules from the LogicMonitor repository to expand and enhance your monitoring coverage.
Monitors AWS Connect metrics from CloudWatch.
Discovers and monitors (via CloudWatch) replication task performance including memory usage, throughput bandwidth, and latency for the AWS Database Migration service. This new DataSource augments existing AWS Database Migration replication monitoring.
Checks to see if port 49 for Cisco ISE TACACS+ is open and alerts if it is not.
Added two new DataSources (Cisco_HyperFlex_NodePerformance and Cisco_HyperFlex_ClusterPerformance) to the Cisco HyperFlex package for node and cluster performance monitoring. Added one new EventSource (Cisco HyperFlex Events) for the capture of Cisco HyperFlex warning, error, and critical events.
Cisco HyperFlex Events
Added two PropertySources (addERI_EMC_ECS_Cluster and addERI_EMC_ECS_Node) and one TopologySource (EMC_ECS_Topology) for enhanced topology mapping coverage.
Note: As detailed in the next section, enhancements have been made to all existing Dell EMC ECS DataSources, also for the purpose of expanding topology support.
New SysOID for mapping of Dell EMC Isilon H500 nodes
LogicMonitor has greatly expanded its out-of-the-box monitoring for Fortinet’s product suite. Brand new coverage for seven Fortinet product lines has been added and coverage for FortiGate has been significantly enhanced.
See Fortinet FortiADC Monitoring for details.
See Fortinet FortiAuthenticator Monitoring for details.
LogicMonitor has released a new monitoring package for Fortigate that vastly expands coverage of Fortigate metrics, as well as the efficiency of data monitoring.
Note: These new DataSources deprecate LogicMonitor’s legacy FortiGate DataSources. For details on setup and migration, see Fortinet FortiGate Monitoring for details.
See Fortinet FortiMail Monitoring for details.
See Fortinet FortiManager Monitoring for details.
See Fortinet FortiSwitch Monitoring for details.
See Fortinet FortiWeb Monitoring for details.
See Fortinet FortiWLC Monitoring for details.
Monitors the health check result for GCP Load Balancer backend instances.
Monitors capacity metrics for Azure Blob Storage services.
Monitors Azure ExpressRoute circuit data bandwidth, and data bandwidth per peering.
Discovers Azure Machine Learning workspaces and monitors workspace performance and job metrics via Azure Monitor.
Azure SQL databases use one of two pricing models: the original DTU model or the newer vCore model. LogicMonitor’s initial DataSource for monitoring Azure SQL was returning data collection errors when attempting to track DTU metrics on vCore-based database instances. To remedy this, we have introduced a new DataSource named Microsoft_Azure_SQLDatabaseNonDTU for use with vCore-based database instances. As discussed in the next section, the original Microsoft_Azure_SQLDatabase DataSource has additionally been updated to target DTU-based instances only.
Added two TopologySources (NetApp_7mode_Topology and NetApp_Cluster_Topology) and one PropertySource (addERI_NetApp) for enhanced topology mapping coverage.
Note: As detailed in the next section, enhancements have been made to several existing NetApp and VMware vCenter LogicModules, also for the purpose of enhancing NetApp topology support.
New out-of-the-box monitoring for VMware vCenter HA (High Availability) finds vCenter clusters with HA configured and monitors various cluster metrics.
Made updates to prevent this PropertySource from incorrectly assigning the “TopoSwitch” system category to resources for which no topology data is returned.
Performed various cleanup, including adding missing datapoint descriptions; added graphs.
Refactoring of Active Discovery and data collection Groovy scripts in order to cache authentication tokens. This was necessary to comply with new authentication limits for generating authentication tokens Cisco implemented beginning with HyperFlex firmware 4.0(2a). This should be a seamless update for all customers running existing Cisco HyperFlex LogicModules, with no data loss expected.
Additionally, unrelated to authentication tokens, wildvalue sanitization was performed on the majority of DataSources in order to fix issues with spaces and invalid characters in the data collection scripts.
Additionally, added backwards support for older API versions to the Cisco_HyperFlex_HypervisorVMS DataSource.
Note: As detailed in the previous section, a new EventSource was also added to this monitoring package.
Added missing ##WILDVALUE## to the physicalSecurity datapoint.
Fixed issue causing No Data / NaN to be returned for authentication and brokering datapoints.
Updated scripts with ERI properties for topology support.
Note: As detailed in the previous section, brand new EMC ECS LogicModules are also available for the purpose of enhancing topology coverage.
Updated the data collection scripts for the Email_RoundTrip and Email_TransitTime DataSources to disable TLS when the smtpType property (as set on the instance) is configured to use port 25. If enabling TLS use when the scripts are configured to use port 25 is required in your environment, an optional property named smtp.force.TLS.25 is now available that, when set to TRUE on the resource, enables TLS when port 25 is implied (smtpType is blank or ”).
Improved the datapoint description and alert message.
As detailed in the previous section, LogicMonitor has released a new monitoring package for Fortinet FortiGate, which effectively serves to deprecate existing FortiGate DataSources.
Note: If you are currently using the now-deprecated DataSources, you will not experience any data loss upon importing the new set of DataSources because of the name variations that exist between the two sets. However, you will collect duplicate data and potentially receive duplicate alerts for as long as both sets of DataSources are active. For this reason, we recommend that you disable the legacy DataSources after you have imported the new ones and verified that they are working as expected. For more information on migrating to the new FortiGate monitoring package, see Fortinet FortiGate Monitoring.
Changed the metric type of the bytesOut and bytesIn datapoints from gauge to derive.
Note: A brand new monitoring suite for Fortinet FortiGate was announced for this release, as detailed in the previous section. If you are downloading the suite for the first time, this update is already present in the Fortinet_FortiGate_ActiveIPSecVPNTunnels DataSource. However, if you have already downloaded it (this suite was made available in mid-April), you’ll want to update this DataSource.
Added datapoints for available topics that were not yet covered.
Update the Exception metrics to use ##primaryaggregation## as .count was no longer working. Additionally, removed the two BillingMetrics_xx metrics from the DataSource as they aren’t listed as Insight components and are not working in customer accounts. See Microsoft’s Supported metrics with Azure monitoring documentation for a list of metrics.
Updated the NetworkIn and NetworkOut datapoints to use Azure’s “Network In Total” and “Network Out Total” metrics, rather than the deprecated “Network In” and “Network Out” metrics; added a link to Azure’s metrics page from the DataSource’s Technical Notes field.
Switched to single quotes on global variables to capture special characters; added TLS 1.2 support; improved exiting of PSSessions to respect the three concurrent session maximum limits recently imposed by Microsoft Office 365.
The AppliesTo statement for both PropertySources has been updated to better target only properly configured Office 365 resources, bypassing issues caused when Office 365 credentials (username and password) are set as properties at a level higher than the resource level in the Resources tree.
Additionally, reverted the previously-set “NoPing” category that these PropertySources were applying so that Office 365 resources are once again pinged.
Additionally, updated the script for the addCategory_Office365Reports PropertySource to capture error codes for improved debugging.
This DataSource has been temporarily removed from the repository due to timeout issues stemming from slow Microsoft PowerShell module performance. We are researching alternative approaches to retrieving these metrics.
Updated the AppliesTo statement to only target database instances that use the DTU pricing model. As detailed in the previous section, a new DataSource named Microsoft_Azure_SQLDatabaseNonDTU has been released for use with vCore-based database instances.
Added ERI properties for the purpose of enhancing NetApp topology mapping support to the following DataSources (and PropertySource): NetApp_7mode_Disks, NetApp_7mode_Volumes, NetApp_Cluster_Disks, NetApp_Cluster_Volumes, VMware_vCenter_HostPerformance, VMware_vCenter_HostStatus, and addERI_ESXi.
Note: The NetApp_Cluster_Disks DataSource update also features an alert threshold update on the ssd_percent_remaining_life datapoint (unrelated to topology mapping).
Note: As detailed in the previous section, brand new NetApp LogicModules are also available for the purpose of enhancing NetApp topology support.
Moved the default alert thresholds from the existing node_state datapoint to the new node_state_alert complex datapoint.
Moved alert threshold for states from the State datapoint to the new stateAlerts complex datapoint.
Added three new datapoints for tracking node health, epsilon, and cluster eligibility.
Removed “finally” from catch block to prevent duplicate extractLldpRemotesWalk call; instructed TopologySource to perform SNMP walks rather than GETs if ExtremeXOS device is detected.
Added a graph for the TotalArrayUsagePercent datapoint; minor script cleanup.
Increased SNMP timeout on walks; cleaned up Active Discover and data collection scripts.
Updated data collection script to handle No Data.
Updated collection code to prevent duplicate alert discovery; updated alert message.
Made updates to the Active Discovery and Collection scripts that create an MD5 hash from the ##WILDVALUE## to prevent special characters from breaking data collection.
Added missing alert thresholds and updated various datapoint descriptions and alert messages for the following DataSources: Viptela_System_CPU, Viptela_System_Fans, Viptela_System_Memory, Viptela_System_PSU, and Viptela_System_Status.
Update data collection script to test for counterMap key existence to address script errors.
Updated the AppliesTo statement to exclude isWindows() devices as VCSA is based on VMware Linux Photon OS.
Reverted the CPUReadyperVCPUPercent datapoint calculation change (which was made in v.134) back to original calculation. Per the VMware Knowledge Base, the original calculation was correctly converting CPU summation percent values.
Fixed issues with the capture of user type codes and user status.
In This Article