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!
v.148 of the LogicMonitor portal is scheduled to roll out to customers from February 17 through March 1.
You can now generate alerts automatically on logs!
This release introduces a new concept called Pipelines, which are used to define filters and processing steps on logs as they are ingested. Pipelines are currently scoped to match one resource, but we’ll expand this scope with an upcoming release.
The first processing step lets you add alert conditions using regular expressions to match the logs in a pipeline.
When log alerts conditions are matched, they trigger standard LogicMonitor alert notifications based on the alert settings (critical, warning, error). You can also view the log alert in the Logs graph, where it will display as a line alongside the alerting log event, and acknowledge the alert in the log list.
You may find this new functionality useful for making logs more actionable, and automating the process of notifying someone when known issues occur.
Recently released to the LogicMonitor public repository, our new and updated LogicModules are available for import to expand and enhance your monitoring coverage.
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.
LogicMonitor is developing a Push Metric API in order to allow metrics to be sent directly to LogicMonitor without the use of a Collector.
The first phase of the beta is continuing and we are now opening up the second phase of the beta which features a Python SDK for the Push Metrics API.
If you are currently participating in the first phase and would like to expand your testing to include the new Python SDK, see the Push Metrics API Solution guide (this guide will be updated shortly with SDK details).
If you are not currently participating in the first phase, please complete the Customer Beta survey and use the comments section to indicate your interest in participating in testing for the Push Metrics API Python SDK.
Available as a beta feature for all Enterprise and Enterprise MSP customer accounts, the Alerts page incorporates a brand new time-series header graph that provides immediate visual insight into an alert storm or other event requiring investigation.
Mirroring the alerts currently displayed in the alert table, this graph’s aggregated alert counts can be grouped by a number of dimensions including alert severity, associated alert triggers (resource, LogicModule, instance, datapoint), matching alert rules, or the escalations chains used to deliver alert notifications.
Available by clicking the more options icon located in the upper right corner of the Alerts page, the header graph is highly interactive, allowing you to zoom in on a time range or use the graph’s legend to quickly include/exclude a group of alerts. As you interactively change the graph’s filters, the alert table will automatically update to remain in sync.
Note: As a beta feature, this header graph may exhibit some performance or functional issues; closing the graph will eliminate any potential impacts you experience when using other aspects of the Alerts page.
For more information on using this new alert header graph, see Managing Alerts from the Alerts Page.
In the following months, LogicMonitor will continue enhancing alert grouping capabilities with the addition of treemap graphs for subgrouping and new grouping dimensions.
In This Article