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!
Providing you with more fine-grained control over allowed user activity, LogicMonitor has introduced two new permissions to its role-based access control (RBAC) system:
Note: Upon rollout of v.139, users with administrator and manager roles will automatically be provisioned with these new permissions. In addition, threshold and SDT permissions will automatically be provisioned for any roles that currently have manage permissions in place for one or more resource groups. For example, if a role previously provided manage permissions for Resource Group X, that role will now provide manage, threshold, and SDT permissions for Resource Group X. Similarly, SDT permissions will be automatically provisioned for any roles that currently have acknowledge permissions (independently of manage permissions) in place for one or more website/resource groups.
Upon your account’s upgrade to v.139, import our new and updated LogicModules from the LogicMonitor public repository to expand and enhance your monitoring coverage.
LogicMonitor has released a new monitoring suite for APC rack PDUs that expands and restructures monitoring. Previously, only PDU load was primarily monitored; with the expanded capabilities made possible by the new suite of DataSources, current, voltage, power on state, and power utilization metrics are additionally monitored. The new suite consists of the following DataSources: APC_rPDU_Banks, APC_rPDU_GlobalPerformance, APC_rPDU_Phases, and APC_rPDU_SwitchedOutlet.
Important: This new monitoring suite deprecates the following legacy APC Rack PDU DataSources: APC Rack PDU Outlet Status-, APC Rack PDU Power Supplies, APCRackPDUBankLoad-, and APCRackPDUPhaseLoad-. If you are currently using these 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.
The new AWS_Elemental_MediaConnect DataSource monitors throughput, requests, and error counts for AWS Elemental MediaConnect flows.
The new AWS_Elemental_MediaPackage DataSource monitors throughput, response codes returned, and response time for AWS Elemental MediaPackage channels.
The new GCP_DeveloperTools_CloudTasks DataSource monitors queue depth, latency and request/attempt counts for Cloud Tasks.
Comprehensive monitoring of the Infinidat InfiniBox enterprise storage system using the InfiniBox REST API. For setup and monitoring details, see Infinidat InfiniBox Monitoring.
The Microsoft_Azure_AppService_Environments_MultiRolePool DataSource monitors pool requests, response time, HTTP return codes, and performance metrics for the Microsoft Azure App Service.
LogicMonitor has released three new ConfigSources that monitor various elements of a Windows DHCP server, alert on changes, and, in some cases, provides a history of IP address assignments. For setup and monitoring details, see Microsoft DHCP Monitoring.
Monitors metrics for Azure Queue storage services (reported hourly by Azure).
Monitors metrics for Azure storage accounts (reported hourly by Azure).
Monitors performance metrics for Azure Table storage services (reported hourly by Azure).
A new DataSource named Oracle_Database_TableSpaceStatus was added to the Oracle monitoring suite. This DataSource discovers Oracle database tablespaces and determines whether they are online, read-only or offline.
LogicMonitor has released a new DataSource named RADIUS_SyntheticTransaction that tests authentication to a RADIUS server. Using provided credentials and a specified authentication protocol, this DataSource initiates a synthetic transaction with the RADIUS server and reports on success status, as well as amount of time for transaction connection (or failure).
Note: Collector version 29.100 (or a higher version number) is required for this DataSource.
LogicMonitor has released five new DataSources for the SwiftStack monitoring suite. In addition to providing greater efficiency and scalability, these DataSources append the cluster UUID for the purpose of making WildValues unique. The new DataSources are: SwiftStack_Cluster_AccountStorageUtlization, SwiftStack_Cluster_AccountTransferUsage, SwiftStack_Cluster_PolicyAccountStorageUtlization, SwiftStack_Cluster_PolicyStorageUtilization, and SwiftStack_Cluster_PolicyUsage.
Important: These new DataSources deprecate the following SwiftStack DataSources: SwiftStack_Cluster_AccountStorageUsage, SwiftStack_Cluster_AccountTransferUtilization, SwiftStack_Cluster_PolicyAccountStorageUsage, SwiftStack_Cluster_PolicyCapacity, and SwiftStack_Cluster_PolicyStorageUsage.
For more information on setup and migration, see SwiftStack Monitoring.
LogicMonitor has released a new DataSource named TACACS_SyntheticTransaction that tests authentication to a TACACS server. Using provided credentials and a specified authentication protocol, this DataSource initiates a synthetic transaction with the TACACS server and reports on success status, as well as amount of time for transaction connection (or failure).
LogicMonitor has released nine new ConfigSources to monitor critical elements of a Windows domain, alert on changes, and, in some cases, alert on deviations from recommended Microsoft best practice. For setup and monitoring details, see Windows Active Discovery Monitoring.
As highlighted in the New Monitoring Coverage section, LogicMonitor has released a new monitoring suite for APC rack PDUs that provides significantly enhanced monitoring. This new monitoring suite deprecates the following legacy APC Rack PDU DataSources: APC Rack PDU Outlet Status-, APC Rack PDU Power Supplies, APCRackPDUBankLoad-, and APCRackPDUPhaseLoad-.
If you are currently using these 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.
Lowered the rejection threshold for temperature estimation to account for erroneous temperature values returned by some ASA devices.
Added support for Cisco Firepower FPR-1140 Security Appliance to the following LogicModules: Cisco_Firepower_Chassis, Cisco_Firepower_CPU, Cisco_Firepower_Fans, Cisco_Firepower_Memory, Cisco_Firepower_PSU, Cisco_Firepower_SecurityModule, Cisco_Firepower_SecurityModule_Filesystems, and addCategory_CiscoFirepowerSNMP.
Changed the sent Referer header to lowercase to accommodate the field’s case sensitivity. Allowed for empty responses from the server.
Updated the Active Discovery script to use serial number instead of device name for WildAlias due to naming conflicts for the following DataSources: Cisco_Meraki_AccessPoint_Interfaces, Cisco_Meraki_AccessPoints, Cisco_Meraki_Gateway_Interfaces, Cisco_Meraki_Gateways, Cisco_Meraki_SecurityAppliance_Interfaces, Cisco_Meraki_SecurityAppliances, Cisco_Meraki_Switch_Interfaces, and Cisco_Meraki_Switches.
Important: Updating to these new DataSource versions will result in loss of historical data due to instance renaming. These DataSources were very recently introduced so data loss will not encompass more than a few weeks of collected data.
Switched “warning” and “minor” severity status codes for several datapoints. Updated error alert thresholds to alert only if the fault has “major” severity. Added filter to exclude FSM related faults.
Remove instance level grouping for improved visibility across all access points; created new complex datapoints (AdminStatusDisabled, AdminStatusEnabled, and OperationStatusDisassociated) to support two new overview graphs.
Removed unnecessary try/catch blocks from all LogicModules in the suite. In addition, the following unique updates were made to the following LogicModules:
Improved the reliability of the data collection script.
Added handling for long filesystem names.
Updated collection script to return 0 for values of minReportLatency and maxReportLatency datapoints that are too high/low.
Updated the aggregation type for the Transactions datapoint to use the Microsoft recommended aggregation type.
Added a datapoint (named provisioningState), graphs, and alert thresholds to capture and alert on the provisioning state of the connection. Updated the egressBytesTransferred and ingressBytesTransferred datapoints to use counter instead of gauge. Added a Top Connections by Throughput overview graph.
Corrected a bad IF statement in the Active Discovery script that was causing discovery to fail.
Included the CPURawNice datapoint in the calculation of the CPUBusyPercent complex datapoint.
Fixed expressions for the WeightedReadLatency and WeightedWriteLatency complex datapoints. Updated both alert messages to indicate that datapoint values are weighted.
Fixed regression that was causing collection and Active Discovery scripts to look for the existence of openmetrics.ssl and openmetrics.maphostname properties instead of the actual value of the properties.
Added “-1” as a status code for the status datapoint to represent the “not_installed” component state.
For the snmpHRDisk- and snmpHRLargeDisk- DataSources, updated the AppliesTo logic to associate with UCOS.
Updated the Active Discovery script to replace “:” with “-” in WildValue. Updated the collection script to prevent WildValue mismatch on collection output.
As highlighted in the New Monitoring Coverage section, LogicMonitor has released five new DataSources for the SwiftStack monitoring suite. These new DataSources deprecate the following SwiftStack DataSources: SwiftStack_Cluster_AccountStorageUsage, SwiftStack_Cluster_AccountTransferUtilization, SwiftStack_Cluster_PolicyAccountStorageUsage, SwiftStack_Cluster_PolicyCapacity, and SwiftStack_Cluster_PolicyStorageUsage.
Fixed script output to include response used for setting the Found datapoint value.
Cleaned up datapoint descriptions, graphs, and alert messages.
This DataSource is a duplicate of the Veeam_BackupAndReplication_Jobs_VMWareSureBackups DataSource and, as such, has been deprecated.
Updated the Active Discovery and collection scripts to use multi-threading for improved performance.
Added graphs for data throughput and packet transmission.
Made updates to facilitate the blocking of duplicate MAC addresses causing topology mapping issues.
Updated misleading statement about AppliesTo in the DataSource Description field.
Updated the AppliesTo logic for Windows LogicModules to exclude association with Windows Server Failover Cluster (WSFC) resources. This will help eliminate the dual alerting that happens with Windows resources that are reporting to the cluster and the node. All of the modules listed next will no longer apply to cluster virtual network names (VNNs) or virtual IP (VIP) addresses. They will only apply to the nodes.
LM Logs makes logs usable when they are needed most, before performance issues result in business problems. This new feature offers a unique and unified approach to log analysis centered on algorithmic root-cause analysis.
Actionable log data is correlated with metrics and presented as context to alerts within LogicMonitor to help you more quickly make the leap from what issues are occurring to why they are occurring, reducing mean time to repair.
Initially, we are looking for beta participants with AWS CloudWatch or S3-based logs to test LM Logs’ AWS integration. However, over the beta period, we’ll make additional integrations available for testing and expand customer eligibility.
LM Logs is entering beta within the next couple of weeks. If you’d like to be considered for participation, fill out the LM Logs Beta form.
Shortly after your portal is updated to v.139, you will see the location of Web Checks and Ping Checks coming from the “US – San Francisco” checkpoint change to reference the new “US – Oregon” checkpoint, which is replacing the San Francisco checkpoint. This update will be seamless and requires no action on your part. All historical data will be retained.
All potential IP addresses are listed in LogicMonitor’s External Testing Locations. Please ensure that your network’s firewall(s) permits access to all IP addresses on this list in order to maintain continued service.
In This Article