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!
Launching on November 18, LM Logs offers a unique and unified approach to log analysis centered on algorithmic root-cause analysis. LM Logs analyzes log events after they are ingested and mapped to a monitored resource to identify normal patterns and deviations from these patterns: anomalies.
Log anomalies represent log events that are new, or seen for the first time on the monitored resource it’s associated with. These anomalies are displayed in two places: (1) the new Logs page, where you can review raw logs and investigate log anomalies across your entire infrastructure and (2) the Graphs tab for alerts, where they are displayed contextually with metric alerts to help speed troubleshooting.
To get logs into LogicMonitor, you can choose from one of our provided integrations or send custom logs directly to the logs ingestion API. For more information, see the LM Logs Documentation.
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 (rather than delete) the deprecated LogicModule after you have imported its replacement to provide time to (1) verify that it is working as expected and (2) build up a new set of historical data.
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.
Beta for Push Metrics API is targeted for December. If you have a compelling use case and the resource availability, and would like to be considered for participation, please complete the Customer Beta survey.
In This Article