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!
Note: To include the accompanying suppression column in your alert table, you’ll need to customize the column settings for your alert table. To learn more about filtering alerts and customizing alert table settings on the Alerts page, see Managing Alerts from the Alerts Page.
Because there is not always an obvious sign that network traffic flow monitoring has been diminished or interrupted, this new widget will serve to provide an earlier warning for time sync issues or high volumes of malformed templates or flows.
Note: This widget requires Collector version 30.100 or greater. Because this version is not yet available, the widget will be auto-collapsed upon release.
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. 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.
The first phase of beta for Push Metrics API is underway! In this first beta phase, a REST API is provided for beta participants that features endpoints for metric ingestion, resource property update, and instance property update.
In the second beta phase (targeted for the later half of Q1 2021), the REST API and a Python SDK will additionally be available for beta participants. We plan on making other language-specific SDKs available soon after.
If you have a compelling use case and the resource availability, and would like to be considered for participation in either the first or second beta phase, please complete the Customer Beta survey. In the comments section please let us know if you would like to use the REST API directly, via Python SDK, or have a request of another language-specific SDK such as Go, Java, or .NET.
In this beta release, we’ve made some cloud integrations available through LM Exchange in your LogicMonitor portal. LM Exchange will make it possible for you to sort and filter for modules by type or status, for example, to see when upgrades are available or to review all the LogicModules available in a package.
Specifically, for this beta, the AWS cloud integration onboarding has received a facelift and can now be initiated from LM Exchange. Microsoft Azure and GCP will follow suit in future releases.
Also, as part of this beta, we are beginning our SaaS API authentication for Office365—with more SaaS solutions (Zoom, SalesForce, and so on) to follow in coming releases. This marks a new method for agentless collection of SaaS application metrics.
If you are interested in participating in the beta program for SaaS integrations, reach out to your LogicMonitor representative. Ideal partners are already leveraging cloud monitoring and are willing and able to integrate with at least one Office 365 subscription and participate in feedback rounds.
In This Article