LogicMonitor v.161 is scheduled to roll out to customer portals from November 15 through November 24.
- Feature Highlights: Added a query language to expand search and filtering capability for logs.
- General Updates: Added advanced filtering in Traces, enhancements to the details captured in audit logs, updates to integrations for Ansible and Autotask, and more.
- Updated Monitoring: New LogicModules to monitor the performance of Cisco Multicast groups, Hypervisor memory on virtual machines, SNMP host uptime, and more.
New Logs Search
With this release, we’ve added a query language to LM Logs to expand your search capabilities beyond keyword searches and filtering by resource, group, pipeline, and time range. With the added flexibility of combining filters with logical operators, filtering events based on fields and values, and using glob expressions and regular expressions to match results, you can narrow down information to quickly find relevant logs when troubleshooting. You can also summarize activity from log messages you receive over a time range for reporting or alerting.
Other changes to the Logs page includes:
- We removed the filtering menus for Resources and Groups because filters can be added directly from the query bar.
- If you don’t know where to start, autocomplete will help you build the query with suggestions for fields, values, and operators based on the information in your logs.
- Searches do not execute automatically. When you’ve finished building your query, click the Search icon to run it.
- You can now view and manage your Recent Searches by clicking the Clock icon to see the last 10 searches in your history.
For more information and examples, see LM Logs Query Language.
Modules snippets are pieces of reusable code that can contain functions, classes, and data. Snippets are used by newer LogicModules to implement common functionality, such as formatting data for the Collector and generating topologies, as well as implement other device-specific code, such as interacting with APIs. Support for snippets requires Collector version 30.000 or higher.
Customers cannot create or deploy snippets on their own. We are in the process of building this feature and will continue to keep you updated as new improvements are implemented.
- Fixed an issue to ensure that searching for LogicModules in the Alerts page does not return an error if the search includes a colon.
- Audit commands now record details when the posh command is run in the Collector debug console.
- Updated the details recorded when adding, updating, deleting, and stopping Scheduled Down Time (SDT) for Collectors and device log pipelines.
- For Collectors, audit logs now include startdowntime, enddowntime, collectorid, and devicename.
- For device log pipelines, audit logs now include startdowntime, enddowntime, devicelogpopelineid, and devicelogpipelinename.
- Audit logs now record the following datapoint details when changes to alert thresholds are made at the instance and device group levels: datapoint ID, datapoint name, and datapoint value.
- Audit logs now record the following details when updating Active Discovery: old value, new value, and instance ID.
- Added filtering and mass selection for Azure subscriptions and permissions in Cloud Integrations settings. This ability will make it easier to select and enable or disable a large number of Azure subscriptions for monitoring and testing.
- Azure VM service limits will now only be monitored for the selected regions and subscriptions to avoid monitoring these limits twice in cases where tenants are added into LogicMonitor multiple times (but with different subscriptions selected).
- Fixed an issue to correctly gather metrics from “Auto Stop” AWS Workspaces
- Updated the Traces page to show root operations by default, instead of all operations. Users can still switch to display all operations. This provides an improved workflow for users as they will be able to drill down into individual poor performance more effectively from a higher-level aggregated view.
- Added advanced filtering on the Traces page. Users now have the ability to search by tags that are ingested with spans. Users can switch between advanced and basic filtering options.
- Added the ability to apply custom configurations when adding a host-based OpenTelemetry Collector in the user interface.
- Fixed an issue where duplicate OpenTelemetry Collector entries were created for Kubernetes installs.
- The URLs in the LogicMonitor integration for Autotask have been updated to access the v.16 Autotask API because of a change that requires all integrations with Autotask to use the credentials for API-only users.
- The LogicMonitor integration for Ansible now supports the ability to install an existing Collector when you explicitly provide the Collector ID.
- With Argus v6 to optimize the performance, a new resource tree is available where resources are grouped under Namespaces and ClusterScoped. For more information, see Updating Kubernetes Resource Tree.
- Added support for a query language for searching logs. See the Feature Highlight.
- Added autocomplete to help build queries. As you type in the query bar, autocomplete will suggest Fields, Values, and Search Operators to based on the information that is available in your logs.
- Added a Recent Search option that will display search history of the last 10 queries. You can also remove and clear the history.
- Added support for LogicModule snippets. Snippets require Collector version 30.000 or higher. See Feature Highlight.
- Expanded the limit in the Technical Notes field in LogicModules from 512 to 4096 characters.
- Added a more detailed error message for attempts to enter an invalid first name or last name when updating existing users.
New and updated LogicModules are available for you to import from the LogicMonitor Public Repository. This section lists the LogicModules that are new in this release, updated in this release, or will be removed in a future release. Changes related to the LogicModule feature will be listed under General Updates.
|(3 DataSources, 1 PropertySource, 1 TopologySource)
Maps and monitors the performance and operational stats of Cisco Multicast groups, interfaces, and routes.
Requires Collector version 30.000 or higher.
See Updated LogicModules for L2 Networking.
Monitors Power Over Ethernet with Cisco-specific OID.
Combined existing uptime modules into a single module to remove duplicate coverage and streamline support.
When SCVMM is used to load balance virtual machines, the Memory pressure and memory utilized will be shifted to this new module. This retains the old module history. The new module only needs to be installed when a load balancer is in use.
Added out-string width to maintain formatting consistency and prevent false alerts on config diff checks.
Updated graphs to display throughput in bps instead of bytes.
Adjusted Active Discovery to omit CPU entries without any data.
Uses V1 of Meraki’s API. Packet counts now use the perSec data coming from the API. A threadpool is used (4) threads to complete in time. PoE data is power used over the last 24 hours. Poll times have been reduced from 30 to 10 min.
Duplicates wildalias values were causing some instances to be ignored. On instances where a duplicate wildalias exists, the wildvalue is now appended to the wildalias to make it unique. This will prevent loss of data for non-duplicate names. Data can be lost in the case of duplicate names, but it’s unknown what interface channel was being monitored in the past.
Added new backup status of kWarning.
Renamed 3 datapoints which were representing data incorrectly. This may lead to data loss. Changed from Kbps to Mbps, and adjusted the complex datapoints to calculate the bytes correctly. Further minor changes were made to graphs.
Added support for SHA-256 authentication via optional host property “msa.sha” (set to true to use this authentication type, otherwise defaults to MD5).
|(1 DataSource, 8 ConfigSources, 6 PropertySources)
Updated “stoppers” (lines that when found immediately mark the collection as a failure) in generic configs to prevent high CPU usage.
Added support for automatically exiting out of several depths of privilege escalation.
Updated Common Configs to provide better filtering and support for checks across more config types (common, dynamic).
Implemented more robust “Interactive” collection.
Changed the type of status datapoint to correct an issue in values reported.
Added auto-delete instances to Active Discovery to reduce instance count and Collector load.
Fixed an issue that prevented the script from completing when it came across an address without self-synced data..
Updated collection with cleaner output.
Updated dp0/coreid0 instance description to remove “Management Plane (MP)” because it was not accurate.
Updated appliesTo to exclude Cisco devices.
|(8 DataSources, 2 PropertySources)
Added new datapoint in Ruckus_SZ_ControllerSummary to represent disk usage as a percent. Increased timeout for script cache to reuse cookie for longer time period.
Fixed casing typo in disk usage API endpoint.
Added Veeam cmdlet version check to ensure proper command is used.
Fixed an issue with logging.
Applied improved discovery logic used in VMStatus utilizing threading for efficiency gains in large environments.
Added a new module to monitor additional sensors that were no longer monitored when switching from Gen 1 to Gen 2 of the VMware suite.
Fixed an issue where the hostname wasn’t passing to all session types.
Updated appliesTo to correct a previous update that excluded too many devices.
Updated to exclude memory data for hypervisors with a load balancer in use. This data is now reported in Win2k12_HyperV_HypervisorMemory for those devices.
Updated appliesTo so it ignores failover cluster virtual name.
Added functionality to detect which OID to use for system uptime used to inform new DataSource SNMP_Host_Uptime.
Added VM detection.
|This update affects L2 Networking Topology and ProperySources, including all 38 addERI_* class of PropertySources.
Leverage snippets for shared data and functions across topology suite. Optimize networking topology to extract layer 2 neighbor data using a specific protocol only if addCategory_TopoSwitch has done so successfully and set an indicative “auto.network.*” property.
All changes require Collector version 30.000 or higher.
See New LogicModules for Cisco Multicast.
Will now only test to see if we can get the version of PowerShell from the remote machine. The Test-WSMAN command was succeeding, but the Invoke-Command was failing as it requires a different level of permissions than Test-WSMan.
|Cisco UCS||(1 Module Snippet)
The request body for login has been updated to accommodate double quotes in passwords.
This table lists LogicModules that we are deprecating in this release. This means that these LogicModules will be removed in a future release. If available, a replacement LogicModule is listed.
|Details||End of Support Date|
Windows_TimeOffset used a collection method that guaranteed a delayed result due to time difference calculation occurring server-side rather than at collection.
The replacement is now scripted with attempts to improve accuracy and better communicate the variation in timing due to time spent on our WMI query.
These modules created excessive instance counts with all runs of a backup, including those that were expired, as separate instances. Data provided was not actionable and created unnecessary collector load.
The replacement modules provide the same data for the latest backups.
Combined existing uptime modules into a single new module to remove duplicate coverage and streamline support.
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.
LogicMonitor APM Lighthouse Program
LogicMonitor APM has been available in a limited release capacity for the past few months. We are now getting ready to expand access with the launch of our Lighthouse Program for users that want access to our APM capabilities.
Along with early access, qualified customers and prospects will have the opportunity to influence the early direction of our product and provide feedback to enhance our APM offering.
If you are interested in participating in our Lighthouse Program, please fill out the Google form here.
RPC API support ends with v.161
Support for the RPC API ends with the release of LogicMonitor v.161. Users have been notified of this in previous releases and should have migrated to the REST API.