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.149 of the LogicMonitor portal is scheduled to roll out to customers from March 8 through March 17.
Highlights:
Collector releases are deployed independently of LogicMonitor platform releases. For more information on the different Collector versions available for upgrade, see Collector Versions.
Note: Users who don’t have access to all resources will only be able to view logs for up to 300 resources when no filters are used on the Logs page. This will be fixed in an upcoming release. To avoid this, use at least one filter as a workaround.
Important: Collector version 29.107 or higher is required for this enhancement; 29.107 has not yet been released.
system.hoststatus
/setting/collector/collectors/{id}
enableFailOverOnCollectorDevice
cucm.api.user
cucm.api.pass
LogicMonitor deprecates LogicModules when 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 may be 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.
Recently released as a beta feature in v.148 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.
Beta for this new header graph will continue in v.149 as we make performance improvements and align the graph filters with the Alerts page filters.
For more information on using this new alert header graph, see Managing Alerts from the Alerts Page.
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, which consists of a REST API that features endpoints for metric ingestion, has been ongoing since early January. The second phase of the beta, which we opened up in early February and includes the addition of a Python SDK, is continuing as well.
If you are interested in 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. 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.
We have decided to focus on improving the LogicMonitor REST API, which has higher security standards and integration capabilities more in-line with our future development goals. This means that we are preparing to end support for the RPC API after this summer. If you are using the RPC API for Ansible, reach out to Support for guidance on migrating playbooks to the REST API.
In This Article
